MySQL query cache crash?

I recently encountered several times of MySQL service crash and restart. We met twice in a row yesterday.

 

The first err log:

1. 81122 16:16:47-mysqld got signal 11;
2. This cocould be because you hit a bug. It is also possible that this binary
3. Or one of the libraries it was linked against is too upt, improperly built,
4. Or misconfigured. This error can also be caused by malfunctioning hardware.
5. We will try our best to scrape up some info that will hopefully help diagnose
6. The problem, but since we have already crashed, something is definitely wrong
7. And this may fail.
9. Key_buffer_size = 536870912
10. Read_buffer_size = 4194304
11. Max_used_connection= 727
12. Max_threads = 1500
13. Threads_connected= 412
14. It is possible that mysqld cocould use up
15. Key_buffer_size + (read_buffer_size + sort_buffer_size) * max_threads = 12827463 K
16. Bytes of memory
17. Hope that's OK; if not, decrease some variables in the equation.
19. Thd: 0x2aad06f7a860
20. Attempting backtrace. You can use the following information to find out
21. Where mysqld died. If you see no messages after this, something went
22. Terribly wrong...
23. Stack_bottom = 0x47118f60 thread_stack 0x40000
24. Trying to get some variables.
25. Some pointers may be invalid and cause the dump to abort...
26. Thd-> query at 0x125b5ae0 = select 'dash'. af
27. From 'dashboard'
28. Where 'dashboard '. uid = '123'
29. Limit 1
30. Thd-> thread_id = 1676832
31. Thd-> killed = not_killed
32. The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
33. Information that shocould help you find out what is causing the crash.
34. Mysqld: my_new.cc: 50: int _ cxa_pure_virtual (): assertion '"pure virtual method called." = "aborted" 'failed.
35. Mysqld: my_new.cc: 50: int _ cxa_pure_virtual (): assertion '"pure virtual method called." = "aborted" 'failed.
36. Mysqld: my_new.cc: 50: int _ cxa_pure_virtual (): assertion '"pure virtual method called." = "aborted" 'failed.
37. Mysqld: my_new.cc: 50: int _ cxa_pure_virtual (): assertion '"pure virtual method called." = "aborted" 'failed.
38. Fatal signal 6 While backtracing
39. Mysqld: my_new.cc: 50: int _ cxa_pure_virtual (): assertion '"pure virtual method called." = "aborted" 'failed.
40. Mysqld: my_new.cc: 50: int _ cxa_pure_virtual (): assertion '"pure virtual method called." = "aborted" 'failed.
41. Mysqld: my_new.cc: 50: int _ cxa_pure_virtual (): assertion '"pure virtual method called." = "aborted" 'failed.
42. Mysqld: my_new.cc: 50: int _ cxa_pure_virtual (): assertion '"pure virtual method called." = "aborted" 'failed.
43. Mysqld: my_new.cc: 50: int _ cxa_pure_virtual (): assertion '"pure virtual method called." = "aborted" 'failed.
44. Mysqld: my_new.cc: 50: int _ cxa_pure_virtual (): assertion '"pure virtual method called." = "aborted" 'failed.
45. 081122 16:16:49 mysqld_safe number of processes running now: 0
46. 081122 16:16:49 mysqld_safe mysqld restarted

This is the second time soon:

1. 081122 17:56:13-mysqld got signal 11;
   This cocould be because you hit a bug. It is also possible that this binary
   Or one of the libraries it was linked against is too upt, 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.
2. 
   
3. Key_buffer_size = 536870912
4. Read_buffer_size = 4194304
5. Max_used_connections = 1
6. Max_threads = 1500
7. Threads_connected = 1
8. It is possible that mysqld cocould use up
9. Key_buffer_size + (read_buffer_size + sort_buffer_size) * max_threads = 12827463 K
10. Bytes of memory
11. Hope that's OK; if not, decrease some variables in the equation.
13. Thd: 0x259d70b0
14. Attempting backtrace. You can use the following information to find out
15. Where mysqld died. If you see no messages after this, something went
16. Terribly wrong...
17. Stack_bottom = 0x45f60f60 thread_stack 0x40000
18. Trying to get some variables.
19. Some pointers may be invalid and cause the dump to abort...
20. Thd-> query at 0x25a2c8e0 = select 'xxxxxxx'. dd
21. From 'xxxxxxxxx'
22. Where 'xxxxxxxx'. FF = ddddddddd
23. Limit 1
24. Thd-> thread_id = 1
25. Thd-> killed = not_killed
26. The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
27. Information that shocould help you find out what is causing the crash.
28. 081122 17:56:13 mysqld_safe number of processes running now: 0
29. 081122 17:56:13 mysqld_safe mysqld restarted

The system has two amd 64-bit CPUs with 16 GB memory. The MySQL version is 5.1.28.

 

The MySQL file information is

/Usr/local/MySQL/bin/MySQL: Elf 64-bit LSB executable, amd x86-64, Version 1 (sysv), for GNU/Linux 2.6.9, statically linked, for GNU/Linux 2.6.9, not stripped

 

Find a similar problem in the MySQL bug Library

Bug #30201 crash with query cache when killing a select

This bug has been fixed in several previous versions.

 

No way, you have to disable the query cache first.