[MDEV-7274] Server crashes in free () from /usr/lib/libjemalloc.so.1 on client connect Created: 2014-12-05 Updated: 2018-08-31 Resolved: 2018-08-31 |
|
| Status: | Closed |
| Project: | MariaDB Server |
| Component/s: | OTHER, Storage Engine - TokuDB |
| Affects Version/s: | 10.1.2 |
| Fix Version/s: | N/A |
| Type: | Bug | Priority: | Major |
| Reporter: | Elena Stepanova | Assignee: | Sergei Golubchik |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Environment: |
Ubuntu Precise 64bit libjemalloc 2.2.5-1, cmake . -DCMAKE_BUILD_TYPE=Debug |
||
| Description |
|
The crash appeared on 10.1 tree since this revision (as soon as 'since' makes sense on git log --topo-order)
The crash only happens if TokuDB is enabled. Out of two machines I tried (Precise and Wheezy), it happens on Precise but not on Wheezy; maybe because the versions of libjemalloc* are different there, or could be some other reason.
|
| Comments |
| Comment by Sergei Golubchik [ 2015-04-27 ] |
|
Yes, I believe I've seen it. This is why our Precise builder has jemalloc 3.6.0. I've even written in KB
In 10.0 we've linked with jemalloc statically, in 10.1 we link with it dynamically ( We either need to link with jemalloc statically on Precise, or use a versioned jemalloc dependency in .deb files. |
| Comment by Sergei Golubchik [ 2015-04-27 ] |
|
It has just occurred to me, do you mean server crashes in buildbot? Or in your own Precise VM where you've built MariaDB with system jemalloc 2.2.5? If the latter, the fix could be — don't use jemalloc if it's older than 2.3 |
| Comment by Elena Stepanova [ 2015-04-27 ] |
|
Neither. I mean perro. I suppose we should just upgrade jemalloc there. |
| Comment by Sergei Golubchik [ 2018-08-31 ] |
|
perro has 3.6.0 now. Closing. |