View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0000022 | Pgpool-II | Bug | public | 2012-08-23 00:34 | 2012-11-15 13:45 |
| Reporter | g.sorbara | Assigned To | nagata | ||
| Priority | high | Severity | crash | Reproducibility | always |
| Status | closed | Resolution | fixed | ||
| Summary | 0000022: *** glibc detected *** pgpool: ... idle in transaction: double free or corruption | ||||
| Description | After a certain amount of time we get the following message from pgpool and the process itself gets stuck and needs to be killed (stop -m fast doesn't work). Connections are estab using jdbc. The only features we use in this case are the new query cache and pooling. Pgpool log doesn't seem to help even with verbosity however we managed to get a valgrind output which I think it's interesting for you developers. | ||||
| Steps To Reproduce | We use jmeters with jdbc sampler. | ||||
| Additional Information | PGPool 3.2.0 RH 6.2 // 2.6.32-220.el6.x86_64 Postgres 9.0.7 | ||||
| Tags | No tags attached. | ||||
|
|
|
|
|
A buffer overrun was fixed. Would you please try the latest V3_2_STALBE version? You can download it from here, by clicking "snapshot" of the top row. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2012-08-23 00:34 | g.sorbara | New Issue | |
| 2012-08-23 00:34 | g.sorbara | File Added: valgrind.zip | |
| 2012-08-28 10:21 | nagata | Assigned To | => nagata |
| 2012-08-28 10:21 | nagata | Status | new => assigned |
| 2012-09-05 20:07 | nagata | Note Added: 0000080 | |
| 2012-11-15 13:45 | nagata | Status | assigned => closed |
| 2012-11-15 13:45 | nagata | Resolution | open => fixed |
