seg faults in NDB/J under load
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
NDB/Bindings |
New
|
Undecided
|
Unassigned |
Bug Description
NDB Java Bindings are extremely unstable under heavy usage eg multiple read
operations across several tables using a single transaction. It seems that
the SWIG layer is directly responsible due to some memory corruption caused
by the native code. Running with debug memory allocator reveals repeatable
errors such as this:
java(15216,
object - object was probably modified after being freed.
which eventually results in SEGV somewhere in NDB native library although
the cause is very likely invalid references passed by SWIG layer there.
some most common backtraces :
*** glibc detected *** /usr/java/
0x0000000060c35220 ***
======= Backtrace: =========
/lib64/
/lib64/
/usr/local/
cluster_
[0x2aaaaec98fd4]
*** glibc detected *** /usr/java/
0x00000000522e7430 ***
======= Backtrace: =========
/lib64/
/lib64/
/lib64/
/usr/java/
/usr/java/
[0x2aaaaea58522]
*** glibc detected *** /usr/java/
0x000000004bbdc530 ***
======= Backtrace: =========
/lib64/
/lib64/
/usr/local/
/usr/local/
/usr/local/
/usr/local/
cluster_
[0x2aaaaea58522]