Bug #44480 mysql crash and will not restart on windows
Submitted: 26 Apr 2009 13:07 Modified: 19 May 2009 13:49
Reporter: Ken Brown Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Server Severity:S1 (Critical)
Version:6.0.10a OS:Windows (Vista)
Assigned to: CPU Architecture:Any
Tags: crash, falcon, Fatal, MySQL

[26 Apr 2009 13:07] Ken Brown
Description:
was attempting to rebuild the database from script when a fatal error happened.  Now database will not restart either from the command line or the service.  This is the second time this has happened and the only way I can readily find to get round it is to uninstall, clear down and reinstall - not ideal

error log reports this
thd: 0x0
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...
090426 14:00:29  InnoDB: Started; log sequence number 0 56683
[Falcon] Error: assertion (lockState == 0) failed at line 132 in file .\SyncObject.cpp

090426 14:00:29 - mysqld got exception 0x80000003 ;
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=0
max_threads=100
thread_count=0
connection_count=0
It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 58261 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

thd: 0x0
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...
007794A0    mysqld.exe!Error::debugBreak()[error.cpp:90]
0077956E    mysqld.exe!Error::error()[error.cpp:73]
007795B9    mysqld.exe!Error::assertionFailed()[error.cpp:78]
0077DA04    mysqld.exe!SyncObject::~SyncObject()[syncobject.cpp:132]
007DD25B    mysqld.exe!Bdb::~Bdb()[bdb.cpp:78]
00871D73    mysqld.exe!`eh vector destructor iterator'()
007D1855    mysqld.exe!Cache::~Cache()[cache.cpp:156]
007D2438    mysqld.exe!Cache::`scalar deleting destructor'()
00793424    mysqld.exe!Database::~Database()[database.cpp:632]
007943C8    mysqld.exe!Database::`scalar deleting destructor'()
007838F3    mysqld.exe!Connection::getDatabase()[connection.cpp:1657]
00783CF6    mysqld.exe!Connection::openDatabase()[connection.cpp:937]
007804FF    mysqld.exe!StorageDatabase::getOpenConnection()[storagedatabase.cpp:151]
00774846    mysqld.exe!StorageHandler::initialize()[storagehandler.cpp:988]
00770DCD    mysqld.exe!StorageInterface::falcon_init()[ha_falcon.cpp:278]
00446555    mysqld.exe!ha_initialize_handlerton()[handler.cc:448]
00575833    mysqld.exe!plugin_initialize()[sql_plugin.cc:1008]
0057A134    mysqld.exe!plugin_init()[sql_plugin.cc:1220]
004DB6FB    mysqld.exe!init_server_components()[mysqld.cc:4138]
004DBF04    mysqld.exe!win_main()[mysqld.cc:4649]
004DC2EB    mysqld.exe!mysql_service()[mysqld.cc:4812]
0086A393    mysqld.exe!_callthreadstart()[thread.c:293]
0086A42C    mysqld.exe!_threadstart()[thread.c:275]
76FE4911    kernel32.dll!BaseThreadInitThunk()
774CE4B6    ntdll.dll!RtlInitializeExceptionChain()
774CE489    ntdll.dll!RtlInitializeExceptionChain()
The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.

How to repeat:
build tables in falcon
create a rebuild script with drop table and create table then execute via cui client.
The build script I was using (from workbench) is attached
[26 Apr 2009 15:21] MySQL Verification Team
Thank you for the bug report. You wrote: "The build script I was using (from workbench) is attached". Could you please attach it?. Thanks in advance.
[26 Apr 2009 16:30] Ken Brown
sorry for the delay.  Firefox crashes when viewing this bug for some reason.

Can get round the re-install now by deleting the falcon fl1, fl2 and fts files - although I'm guessing you may have wanted to see them but they have been secure erased now.
[28 Apr 2009 15:31] Jeff Hood
I'm getting the same exception in WXP SP2. I installed 6.0.10-alpha-community MySQL Community Server yesterday, but was unable to get the GUI interface to work at all. I got the server running on the back-end, can run/execute commands via the command line, and was able to get Open Office to connect successfully yesterday as well as today.

steps to reproduce: I'm unsure. I executed several identical queries. Some worked, some did not. 

from my error log:

090428 10:11:56  InnoDB: Started; log sequence number 0 5874025
Serial Log possible gap: 5103 - 1071
090428 10:11:57 [Note] Event Scheduler: Loaded 0 events
090428 10:11:57 [Note] C:\Program Files\MySQL\MySQL Server 6.0\bin\mysqld: ready for connections.
Version: '6.0.10-alpha-community'  socket: ''  port: 3306  MySQL Community Server (GPL)
[Falcon] Error: assertion (page->pageType == PAGE_sections || page->pageType == 0) failed at line 208 in file .\Section.cpp

090428 10:12:52 - mysqld got exception 0x80000003 ;
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=14680064
read_buffer_size=65536
max_used_connections=1
max_threads=100
thread_count=1
connection_count=1
It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 46997 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

thd: 0x5360fc8
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...
007794A0    mysqld.exe!Error::debugBreak()[error.cpp:90]
0077956E    mysqld.exe!Error::error()[error.cpp:73]
007795B9    mysqld.exe!Error::assertionFailed()[error.cpp:78]
007C21CA    mysqld.exe!Section::getSectionPage()[section.cpp:208]
0079F823    mysqld.exe!Mutex::Mutex()[mutex.cpp:51]
007C27E7    mysqld.exe!Section::getSectionRoot()[section.cpp:1238]
007C2A0B    mysqld.exe!Section::Section()[section.cpp:93]
007BA37B    mysqld.exe!Dbb::findSection()[dbb.cpp:379]
00787BB8    mysqld.exe!Table::findSections()[table.cpp:3716]
0078AA27    mysqld.exe!Table::fetchNext()[table.cpp:505]
0077EBDF    mysqld.exe!StorageDatabase::nextRow()[storagedatabase.cpp:282]
007787FA    mysqld.exe!StorageTable::next()[storagetable.cpp:161]
00771089    mysqld.exe!StorageInterface::rnd_next()[ha_falcon.cpp:638]
004F4336    mysqld.exe!rr_sequential()[records.cc:390]
0058777F    mysqld.exe!join_init_read_record()[sql_select.cc:17028]
005A22DF    mysqld.exe!sub_select()[sql_select.cc:16222]
005A3283    mysqld.exe!do_select()[sql_select.cc:15786]
005A6E59    mysqld.exe!JOIN::exec()[sql_select.cc:2463]
005AAC18    mysqld.exe!mysql_select()[sql_select.cc:3064]
005AB05B    mysqld.exe!handle_select()[sql_select.cc:314]
00563F20    mysqld.exe!execute_sqlcom_select()[sql_parse.cc:4757]
00565DE5    mysqld.exe!mysql_execute_command()[sql_parse.cc:2008]
7C910732    ntdll.dll!RtlAllocateHeap()
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort...
thd->query at 053F6B58= (query removed - I can provide this upon request - jeff)
thd->thread_id=1
thd->killed=NOT_KILLED
[29 Apr 2009 7:46] Sveta Smirnova
Thank you for the report.

I can not repeat described behavior.

Please provide your configuration file, full error log file and indicate if you are running 64-bit or 32-bit machine.
[29 Apr 2009 17:56] Ken Brown
Am on 32bit
[29 Apr 2009 20:28] Jeff Hood
I am on 32 bit WXP
[19 May 2009 0:17] MySQL Verification Team
Thank you for the feedback. I was able to repeat with the release binary I will test with latest source server:

Version: '6.0.10-alpha-community'  socket: ''  port: 3307  MySQL Community Server (GPL)
090518 21:10:05 - mysqld got exception 0xe06d7363 ;
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=54525952
read_buffer_size=65536
max_used_connections=1
max_threads=100
thread_count=1
connection_count=1
It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 86189 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

thd: 0x5e96330
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...
0000000077737FFD    kernel32.dll!RaiseException()
00000001405766A0    mysqld.exe!__CxxCallCatchBlock()[frame.cpp:1357]
0000000077A19221    ntdll.dll!RtlRestoreContext()
000000014044D7C4    mysqld.exe!Database::prepareStatement()[database.cpp:1131]
000000014043BFCA    mysqld.exe!Connection::prepareStatement()[connection.cpp:235]
000000014042CF39    mysqld.exe!StorageTableShare::lookupPathName()[storagetableshare.cpp:789]
000000014042D7D9    mysqld.exe!StorageTableShare::tableExists()[storagetableshare.cpp:778]
000000014042B3CA    mysqld.exe!StorageHandler::createTable()[storagehandler.cpp:659]
0000000140427A60    mysqld.exe!StorageInterface::create()[ha_falcon.cpp:822]
000000014005459B    mysqld.exe!ha_create_table()[handler.cc:3533]
000000014024EEE9    mysqld.exe!rea_create_table()[unireg.cc:496]
0000000140227E62    mysqld.exe!mysql_create_table_no_lock()[sql_table.cc:3706]
0000000140228347    mysqld.exe!mysql_create_table()[sql_table.cc:3860]
00000001401B6C18    mysqld.exe!mysql_execute_command()[sql_parse.cc:2619]
00000001401BB2ED    mysqld.exe!mysql_parse()[sql_parse.cc:5757]
00000001401BBF5B    mysqld.exe!dispatch_command()[sql_parse.cc:1011]
00000001401BD1EC    mysqld.exe!do_command()[sql_parse.cc:691]
000000014026DFB5    mysqld.exe!handle_one_connection()[sql_connect.cc:1146]
00000001402F9D0E    mysqld.exe!pthread_start()[my_winthread.c:63]
0000000140554847    mysqld.exe!_callthreadstartex()[threadex.c:348]
000000014055491F    mysqld.exe!_threadstartex()[threadex.c:326]
000000007773C3BD    kernel32.dll!BaseThreadInitThunk()
0000000077A04581    ntdll.dll!RtlUserThreadStart()
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort...
thd->query at 0000000022921F98=CREATE  TABLE IF NOT EXISTS `Plan`.`P_PLAN` (
  `PLAN_PK` BIGINT UNSIGNED NOT NULL DEFAULT 1 COMMENT 'Internal ID used to reference plan' ,
  `SESSION_ID` BIGINT UNSIGNED NOT NULL DEFAULT 1 COMMENT 'session id performing the create or last update' ,
  `CREATE_NAME` VARCHAR(77) NOT NULL DEFAULT 'Plan' COMMENT 'user who created record' ,
  `CREATE_STAMP` DATETIME NOT NULL DEFAULT '1901-01-01' COMMENT 'stamp when record created\n' ,
  `UPDATE_NAME` VARCHAR(77) NOT NULL DEFAULT 'Plan' COMMENT 'user who applied latest update' ,
  `UPDATE_STAMP` DATETIME NOT NULL DEFAULT '1901-01-01' COMMENT 'stamp when record last updated' ,
  `PLAN_TYPE` VARCHAR(45) NOT NULL COMMENT 'type of plan\nProcess - sub plan for specific process\nProgramme - collection of planning objects\nProject - project plan\nSupport - BAU support plan\nTemplate - Template to generate plans' ,
  `PLAN_STATUS` VARCHAR(45) NOT NULL COMMENT 'Crrent status of the plan\nActive - being worked on\nDormant - Not currently in use\nClosed - All activities compl
thd->thread_id=1
thd->killed=NOT_KILLED
The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.
[19 May 2009 13:49] MySQL Verification Team
Thank you for your bug report. This issue has been committed to our source repository of that product and will be incorporated into the next release.

If necessary, you can access the source repository and build the latest available version, including the bug fix. More information about accessing the source trees is available at

    http://dev.mysql.com/doc/en/installing-source.html