MySQL Bugs: #46647: Keep getting Assertion failure

Bug #46647	Keep getting Assertion failure
Submitted:	11 Aug 2009 10:47	Modified:	11 Sep 2009 11:20
Reporter:	zohar aharoni	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL Server: General	Severity:	S1 (Critical)
Version:	5.1.33	OS:	Linux (CentOS release 5.2)
Assigned to:		CPU Architecture:	Any
Tags:	crash

Description:
Hi,
Not so long ago I moved to 5.1.33 from 5.1.28.
Since than - once in a while the DB is crashing while running SQL queries (Assertion failure).

I managed to overcome some of this cases by changing the execution plan (changing/adding indexes...)

I tried to create simple scenario to reproduce the last crash on clean environment but I couldn't, I guess that It needs the data as well but I cannot deliver it...

Do you have any suggestion on how to further investigate it?

Thanks,
Zohar

How to repeat:
couldn't reproduce on clean environment...

len 224; hex b8e8d9b0aa2a0000fb981375ab2a000072656d656e747371007e00063f50be2903000000000000000300000000000000000000000000000003000000000000000100000000000000
0000000000000000010000000000000000000000000000007b975d52fb71ee2e247400067370726f010000000000000083445107000000000000000000000000000000000000000001000000000000
0030931532ac2a00000000000000000000350000000000000060e11177000000000400000000000000c0c37f50ac2a00006274000373636d7300000000000000000c00000000000000; asc      *
     u *  rementsq ~  ?P )                                                                { ]R q .$t  spro         DQ                             0  2 *
    5       `  w               P *  bt  scms                ;TRANSACTION 0 707966035, ACTIVE 30 sec, process no 19287, OS thread id 1217599808 unlock_row, thr
ead declared inside InnoDB 500
mysql tables in use 22, locked 1
3 lock struct(s), heap size 1216, 1 row lock(s)
MySQL thread id 79576, query id 13725806 localhost 127.0.0.1 trc Sending data
select * from (
select distinct v.id vid
from trc.vids v, test.surls su
where v.pid = 25
        and v.wr = false
        and v.url = su.url) vids
where not exists (select 1 from trc.vidchs vc where cid = 1308088 and vc.vid = vid)
090811 13:31:16  InnoDB: Assertion failure in thread 1217599808 in file btr/btr0pcur.c line 217
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.1/en/forcing-recovery.html
InnoDB: about forcing recovery.
090811 13:31:16 - 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=67108864
read_buffer_size=4194304
max_used_connections=424
max_threads=512
threads_connected=237
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 4265044 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

thd: 0x2aac4e7c1610
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 = 0x48930f20 thread_stack 0x40000
/usr/sbin/mysqld(my_print_stacktrace+0x2e)[0x84417e]
/usr/sbin/mysqld(handle_segfault+0x322)[0x5bc292]
/lib64/libpthread.so.0[0x33ece0de70]
/lib64/libc.so.6(gsignal+0x35)[0x33ec230155]

Thank you for the bug report. Please see bugs: http://bugs.mysql.com/bug.php?id=44959 and http://bugs.mysql.com/bug.php?id=39320 probably duplicate of these. Thanks in advance.

No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".