Bug #35350 Crash when running sysbench oltp test
Submitted: 17 Mar 2008 19:08 Modified: 21 Aug 2008 8:51
Reporter: Sveta Smirnova Email Updates:
Status: Can't repeat Impact on me:
None 
Category:MySQL Server Severity:S3 (Non-critical)
Version:6.0 BK OS:Linux (64-bit)
Assigned to: CPU Architecture:Any

[17 Mar 2008 19:08] Sveta Smirnova
Description:
Verifying bug #34399 and bug #35327 catched crash:

080317 18:40:13  InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
080317 18:40:14  InnoDB: Started; log sequence number 0 263641868
080317 18:40:14 [Note] Event Scheduler: Loaded 0 events
080317 18:40:14 [Note] ./libexec/mysqld: ready for connections.
Version: '6.0.5-alpha'  socket: '/tmp/mysql_ssmirnova.sock'  port: 33050  Source
distribution
080317 18:40:28 - mysqld got signal 11;
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=16384
read_buffer_size=262144
max_used_connections=152
max_threads=151
threads_connected=152
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 49797 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...
frame pointer is NULL, did you compile with
-fomit-frame-pointer? Aborting backtrace!
The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.

How to repeat:
1. Compile MySQL with
CFLAGS="-O3" CXX=gcc CXXFLAGS="-O3 -felide-constructors -fno-exceptions -fno-rtti" ./configure  --prefix=/home/mysql/mysql --with-extra-charsets=complex --enable-thread-safe-client --enable-local-infile --enable-assembler --disable-shared --with-plugins=innobase --with-fast-mutexes --with-libevent 
2. sysbench --test=oltp --oltp-read-only=off --oltp-dist-type=special --num-thread=512 --oltp-table-size=1000000 --mysql-db=sbtest --max-requests=0 --max-time=600 prepare
3. sysbench --test=oltp --oltp-read-only=off --oltp-dist-type=special --num-thread=512 --oltp-table-size=1000000 --mysql-db=sbtest --max-requests=0 --max-time=600 run
[21 Aug 2008 8:51] Sveta Smirnova
I used standard my-small.cnf file with increased max-connections. Bug is not repeatable with current development sources. So I close the report as "Can't repeat"