Bug #26311 falcon crashes in the serial log gopher thread
Submitted: 13 Feb 2007 10:02 Modified: 17 Feb 2007 16:56
Reporter: Shane Bester (Platinum Quality Contributor) Email Updates:
Status: Can't repeat Impact on me:
None 
Category:MySQL Server: Falcon storage engine Severity:S3 (Non-critical)
Version:5.2.3-falcon-alpha-debug OS:Linux (suse9.3 x86)
Assigned to: CPU Architecture:Any
Tags: crash

[13 Feb 2007 10:02] Shane Bester
Description:
Got a repeatable crash when doing some simple queries in a few threads:

FLUSH TABLES...
INSERT IGNORE INTO ...
REPLACE INTO ...
SELECT * FROM .. LIMIT..

Version: '5.2.3-falcon-alpha-debug'  socket: '/tmp/mysql.sock'  port: 3306  yes
database open failed: can't open file "/home/sbester/server/5.2/mysql-5.2.3-falcon-alpha-linux-i686/data/test.fts": No such file or directory (2)
mysqld got signal 4;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.
We will try our best to scrape up some info that will hopefully help diagnose
the problem, but since we have already crashed, something is definitely wrong
and this may fail.

key_buffer_size=8388572
read_buffer_size=131072
max_used_connections=67
max_connections=151
threads_connected=67
It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 336762 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

thd: 0x0
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
Cannot determine thread, fp=0x4407a36c, backtrace may not be correct.
Stack range sanity check OK, backtrace follows:
0x81f5637 handle_segfault + 417
0xffffe410 _end + -142426112
0x83a9308 _ZN5Error10debugBreakEv + 18
0x83a927f _ZN5Error5errorEPKcz + 87
0x8405577 _ZN5Cache9fetchPageEP3Dbbi8PageType8LockType + 587
0x83a26d2 _ZN3Dbb9fetchPageEi8PageType8LockType + 48
0x83a27f5 _ZN3Dbb11handoffPageEP3Bdbi8PageType8LockType + 39
0x83b7e54 _ZN13IndexRootPage17findInsertionLeafEP3DbbiP8IndexKeyij + 450
0x83b9761 _ZN13IndexRootPage10indexMergeEP3DbbiP14SRLUpdateIndexj + 401
0x83f4d0c _ZN14SRLUpdateIndex7executeEv + 154
0x83f4c37 _ZN14SRLUpdateIndex6commitEv + 81
0x83e4732 _ZN20SerialLogTransaction6commitEv + 122
0x83e4903 _ZN20SerialLogTransaction8doActionEv + 23
0x83e1528 _ZN9SerialLog12gopherThreadEv + 256
0x83e1425 _ZN9SerialLog12gopherThreadEPv + 17
0x83849fd _ZN6Thread6threadEv + 67
0x838499c _ZN6Thread6threadEPv + 18
0x40250aa7 _end + 933750423
0x401e6c2e _end + 933316638
New value of fp=(nil) failed sanity check, terminating stack trace!
Please read http://dev.mysql.com/doc/mysql/en/using-stack-trace.html and follow instructions on how to resolve the stack trace. Resolved
stack trace is much more helpful in diagnosing the problem, so please do 
resolve it
The manual page at http://www.mysql.com/doc/en/Crashing.html contains
information that should help you find out what is causing the crash.

Number of processes running now: 0
070213 11:55:07  mysqld restarted

How to repeat:
will upload standalone testcase shortly.
ran tester with parameters --host=192.168.250.2:3306 --database=test --user=root --queryfile=falcon.query --threads=65 --duration=1600 --shuffle-queries=1

Suggested fix:
don't crash
[17 Feb 2007 16:56] MySQL Verification Team
on todays BK 5.2.4, i cannot get a crash using the original testcase. instead, i get an infinite hangup sometimes. I upload the testcase for reference purposes only.
[17 Feb 2007 16:59] MySQL Verification Team
testcase that originally crashed. memory usage seems highly unstable, with sporadic increases/decreases.

Attachment: bug26311.c (text/plain), 10.85 KiB.