Crash from failed assertion in dict0dict.c
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Percona patches |
Fix Released
|
High
|
Unassigned | ||
Percona-XtraDB |
Fix Released
|
High
|
Unassigned |
Bug Description
Server version: 5.0.84-b18-log (MySQL Percona Edition, Revision 57)
Using the same my.cnf we have been using with the ubuntu build 5.0.67, with the exception of adding innodb_
InnoDB: Error: Waited for 590 secs for hash index ref_count (1) to drop to 0.
index: "PRIMARY" table: "halofanon/
InnoDB: Error: Waited for 595 secs for hash index ref_count (1) to drop to 0.
index: "PRIMARY" table: "halofanon/
InnoDB: Error: Waited for 600 secs for hash index ref_count (1) to drop to 0.
index: "PRIMARY" table: "halofanon/
090814 17:08:33InnoDB: Assertion failure in thread 139810549901648 in file dict0dict.c line 1661
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://
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://
InnoDB: about forcing recovery.
090814 17:08:33 - 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_
read_buffer_
max_used_
max_connections
threads_
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
thd=0x7f2816649800
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=0x7f2816649800, backtrace may not be correct.
Bogus stack limit or frame pointer, fp=0x7f2816649800, stack_bottom=
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort...
thd->query at 0x34ec1ae0 = SELECT /* UnusedimagesPag
thd->thread_
Related branches
Changed in percona-patches: | |
status: | Confirmed → Fix Committed |
Changed in percona-xtradb: | |
status: | Confirmed → Fix Committed |
Changed in percona-xtradb: | |
status: | Fix Committed → Fix Released |
Changed in percona-patches: | |
status: | Fix Committed → Fix Released |
"--skip- innodb- adaptive- hash-index" should avoid the crash.... dict_size_ limit, until I will fix it.
Please use it when you use innodb_
Thank you