Bug #50100 Innodb Crash when running SHOW TABLE STATUS
Submitted: 6 Jan 2010 12:32 Modified: 11 Feb 2010 7:15
Reporter: Steven Hartland Email Updates:
Status: No Feedback Impact on me:
None 
Category:MySQL Server: InnoDB storage engine Severity:S2 (Serious)
Version:5.0.89-community-nt OS:Windows
Assigned to: CPU Architecture:Any
Tags: crash, innodb

[6 Jan 2010 12:32] Steven Hartland
Description:
When running the query show table status the server crashes:
100106 11:48:45 - mysqld got exception 0xc0000005 ;
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=26214400
read_buffer_size=65536
max_used_connections=1
max_connections=10
threads_connected=1
It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 28800 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

thd=07005CA8
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...
006629C3    mysqld-nt.exe!row_sel_field_store_in_mysql_format()[row0sel.c:2396]
00662D36    mysqld-nt.exe!row_sel_store_mysql_rec()[row0sel.c:2512]
006644BE    mysqld-nt.exe!row_search_for_mysql()[row0sel.c:3941]
006965CB    mysqld-nt.exe!os_fast_mutex_lock()[os0sync.c:693]
0065429E    mysqld-nt.exe!srv_conc_enter_innodb()[srv0srv.c:1017]
00441006    mysqld-nt.exe!ha_innobase::index_last()[ha_innodb.cc:4173]
004435DE    mysqld-nt.exe!ha_innobase::innobase_read_and_init_auto_inc()[ha_innodb.cc:6914]
00445678    mysqld-nt.exe!ha_innobase::info()[ha_innodb.cc:5559]
0056A853    mysqld-nt.exe!get_schema_tables_record()[sql_show.cc:2523]
0057422C    mysqld-nt.exe!get_all_tables()[sql_show.cc:2393]
00561D74    mysqld-nt.exe!remove_const()[sql_select.cc:6830]
00568420    mysqld-nt.exe!JOIN::exec()[sql_select.cc:1617]
005699F4    mysqld-nt.exe!mysql_select()[sql_select.cc:2350]
00569E3B    mysqld-nt.exe!handle_select()[sql_select.cc:257]
0053B822    mysqld-nt.exe!mysql_execute_command()[sql_parse.cc:2899]
00542721    mysqld-nt.exe!mysql_parse()[sql_parse.cc:6460]
0054371E    mysqld-nt.exe!dispatch_command()[sql_parse.cc:1961]
005449E6    mysqld-nt.exe!do_command()[sql_parse.cc:1644]
00544D05    mysqld-nt.exe!handle_one_connection()[sql_parse.cc:1233]
005F6FEB    mysqld-nt.exe!pthread_start()[my_winthread.c:85]
006E22FF    mysqld-nt.exe!_threadstart()[thread.c:196]
7C80B729    kernel32.dll!GetModuleFileNameA()
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort...
thd->query at 07012870=SHOW TABLE STATUS LIKE 'fileplay_feature'
thd->thread_id=1

It appears as though the table must be corrupted in some way but as innodb doesnt support a repair option there isnt anyway to recover.

How to repeat:
Perform a show table status on the affected table
[11 Jan 2010 7:15] Sveta Smirnova
Thank you for the report.

Could you please send us your ib* files compressed? Or output of SHOW CREATE TABLE fileplay_feature if you can't.
[12 Feb 2010 0:00] Bugs System
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".