Failing assertion: lock != ctx->wait_lock

Bug #1364840 reported by Teemu Ollakka on 2014-09-03
16
This bug affects 3 people
Affects Status Importance Assigned to Milestone
MySQL patches by Codership
Status tracked in 5.6
5.5
Undecided
Unassigned
5.6
High
Seppo Jaakola
Percona XtraDB Cluster moved to https://jira.percona.com/projects/PXC
Status tracked in 5.6
5.5
Invalid
Undecided
Unassigned
5.6
Fix Released
Undecided
Unassigned

Bug Description

From nightly builds randgen load:

2014-09-03 08:06:51 7f9ff8751700 InnoDB: Assertion failure in thread 140325044950784 in file lock0lock.cc line 3948
InnoDB: Failing assertion: lock != ctx->wait_lock
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
08:06:51 UTC - mysqld got signal 6 ;
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=8388608
read_buffer_size=131072
max_used_connections=14
max_threads=151
thread_count=13
connection_count=13
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 68321 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x3780f60
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...
stack_bottom = 7f9ff8750e78 thread_stack 0x40000
/home/vagrant/codership-mysql/build_debug/sql/mysqld(my_print_stacktrace+0x38)[0xad9877]
/home/vagrant/codership-mysql/build_debug/sql/mysqld(handle_fatal_signal+0x3f3)[0x749901]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x10340)[0x7fa00bac7340]
/lib/x86_64-linux-gnu/libc.so.6(gsignal+0x39)[0x7fa00af07f79]
/lib/x86_64-linux-gnu/libc.so.6(abort+0x148)[0x7fa00af0b388]
/home/vagrant/codership-mysql/build_debug/sql/mysqld[0xbb7135]
/home/vagrant/codership-mysql/build_debug/sql/mysqld[0xbb7bab]
/home/vagrant/codership-mysql/build_debug/sql/mysqld[0xbb7fc1]
/home/vagrant/codership-mysql/build_debug/sql/mysqld[0xbb35ab]
/home/vagrant/codership-mysql/build_debug/sql/mysqld[0xbb4247]
/home/vagrant/codership-mysql/build_debug/sql/mysqld[0xbb4542]
/home/vagrant/codership-mysql/build_debug/sql/mysqld[0xbbe904]
/home/vagrant/codership-mysql/build_debug/sql/mysqld[0xc3f491]
/home/vagrant/codership-mysql/build_debug/sql/mysqld[0xc40c6e]
/home/vagrant/codership-mysql/build_debug/sql/mysqld[0xc4135b]
/home/vagrant/codership-mysql/build_debug/sql/mysqld[0xc42736]
/home/vagrant/codership-mysql/build_debug/sql/mysqld[0xc42a36]
/home/vagrant/codership-mysql/build_debug/sql/mysqld[0xc42d17]
/home/vagrant/codership-mysql/build_debug/sql/mysqld[0xc4301b]
/home/vagrant/codership-mysql/build_debug/sql/mysqld[0xc433a0]
/home/vagrant/codership-mysql/build_debug/sql/mysqld[0xc5a3f6]
/home/vagrant/codership-mysql/build_debug/sql/mysqld[0xb5f0c7]
/home/vagrant/codership-mysql/build_debug/sql/mysqld(_ZN7handler12ha_write_rowEPh+0x1a1)[0x6625d7]
/home/vagrant/codership-mysql/build_debug/sql/mysqld(_Z12write_recordP3THDP5TABLEP9COPY_INFOS4_+0xbb9)[0x7dd370]
/home/vagrant/codership-mysql/build_debug/sql/mysqld(_Z12mysql_insertP3THDP10TABLE_LISTR4ListI4ItemERS3_IS5_ES6_S6_15enum_duplicatesb+0x10cf)[0x7db129]
/home/vagrant/codership-mysql/build_debug/sql/mysqld(_Z21mysql_execute_commandP3THD+0x34d6)[0x7ff2e6]
/home/vagrant/codership-mysql/build_debug/sql/mysqld(_Z11mysql_parseP3THDPcjP12Parser_state+0x427)[0x808659]
/home/vagrant/codership-mysql/build_debug/sql/mysqld[0x807c70]
/home/vagrant/codership-mysql/build_debug/sql/mysqld(_Z16dispatch_command19enum_server_commandP3THDPcj+0x102b)[0x7f992e]
/home/vagrant/codership-mysql/build_debug/sql/mysqld(_Z10do_commandP3THD+0x663)[0x7f845d]
/home/vagrant/codership-mysql/build_debug/sql/mysqld(_Z24do_handle_one_connectionP3THD+0x1be)[0x7bee02]
/home/vagrant/codership-mysql/build_debug/sql/mysqld(handle_one_connection+0x33)[0x7be905]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x8182)[0x7fa00babf182]
/lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x7fa00afcc30d]

Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (7f9fb0099dd0): REPLACE INTO `table1000_innodb_int` ( `c0` ) VALUES ( 28573696 )
Connection ID (thread ID): 11
Status: NOT_KILLED

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.

Seppo Jaakola (seppo-jaakola) wrote :

Fix was merged in wsrep-5.6 main branch in revision:
http://bazaar.launchpad.net/~codership/codership-mysql/5.6/revision/4148

Seppo Jaakola (seppo-jaakola) wrote :

Sorry a mistake above -

Fix was merged in wsrep-5.6 main branch in revision:
http://bazaar.launchpad.net/~codership/codership-mysql/5.6/revision/4149

Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PXC-1727

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers