[CONPY-144] ConnectionPool segmentation fault, ping Created: 2021-02-28 Updated: 2021-03-11 Resolved: 2021-03-10 |
|
| Status: | Closed |
| Project: | MariaDB Connector/Python |
| Component/s: | Generic |
| Affects Version/s: | 1.0.5, 1.0.6 |
| Fix Version/s: | 1.0.7 |
| Type: | Bug | Priority: | Critical |
| Reporter: | Lee Clemens | Assignee: | Georg Richter |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | SEGV | ||
| Environment: |
CentOS 7 |
||
| Description |
|
Hello, While I am using the python connector, it may not be the best Project to file this under. Please let me know if I should file it somewhere else or move it as necessary. I am seeing segfaults after 1-2 iterations of fetching connections from a ConnectionPool. It happens after the third connection is re-fetched from the pool most of the time (excluding pool_size=1). I originally thought it was due to my call to .ping(), but it is reproducible without explicitly calling ping() in the test code below (seems to be same stack, I believe ping is called internally regardless).
Both Python versions segfault from the same line: https://gist.github.com/leeclemens/0795d957588410f69fc0a6453ecec94f If the pool_size is > 1, it seems to occur during the pool_size + 3 loop (see comment in gist).
|
| Comments |
| Comment by Georg Richter [ 2021-03-10 ] |
|
Fied in rev. fdee5137d547fc845441233125cc8b31dcea8e23 |
| Comment by Lee Clemens [ 2021-03-11 ] |
|
This looks good, thanks! I see the version number was bumped, but does the tag need to be pushed as well to generate a new release? |
| Comment by Georg Richter [ 2021-03-11 ] |
|
No, tag will be added before releasing. Usually the version number will be bumped after each release - In this case I bumped it, but forgot to commit it (instead it was committed together with this fix). |