5.5.13 Assertion failure on RPL tests

Bug #781471 reported by Valentine Gostev on 2011-05-12
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Laurynas Biveinis

Bug Description

Multiple replication tests fail when we use pool of threads with this assertion failure

110512 1:22:52 InnoDB: Assertion failure in thread 1100896576 in file row0mysql.c line 1133
InnoDB: Failing assertion: trx->mysql_thread_id == os_thread_get_curr_id()
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.5/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
110512 1:22:52 - 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.

It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 10896 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x33d33c0
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 = 0x419e5118 thread_stack 0x40000

Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (0x3419b70): INSERT INTO t1 VALUES (1),(2),(3)
Connection ID (thread ID): 2

description: updated
Changed in percona-projects-qa:
milestone: none → 5.5.13-eb
assignee: nobody → Laurynas Biveinis (laurynas-biveinis)
description: updated
Changed in percona-projects-qa:
status: New → Fix Committed
importance: Undecided → High
Changed in percona-projects-qa:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers