| Bug #25136 | crash occurred after rollingback and inserting more rows | ||
|---|---|---|---|
| Submitted: | 18 Dec 2006 10:39 | Modified: | 19 Jan 2007 21:50 |
| Reporter: | James Bond | Email Updates: | |
| Status: | No Feedback | Impact on me: | |
| Category: | MySQL Server: General | Severity: | S3 (Non-critical) |
| Version: | 5.0.27 | OS: | Windows (WinXP) |
| Assigned to: | CPU Architecture: | Any | |
| Tags: | crash | ||
[18 Dec 2006 10:40]
James Bond
MySQL minidump file
Attachment: mysqld.dmp (application/octet-stream, text), 26.72 KiB.
[19 Dec 2006 8:14]
MySQL Verification Team
James, it looks like an innodb assertion. Please examine the error log, or event viewer and check if innodb printed more details? mysqld!srv_error_monitor_thread+0xd0 kernel32!BaseThreadStart+0x37 005bd9b5 e8463b0000 call mysqld!ut_dbg_assertion_failed (005c1500) 005bd9ba 8b15fce08400 mov edx,[mysqld!ut_dbg_null_ptr (0084e0fc)] 005bd9c0 8b02 mov eax,[edx] ds:0023:00000000=???????? 005bd9c2 83c418 add esp,0x18 005bd9c5 3bc6 cmp eax,esi 005bd9c7 740c jz mysqld!srv_error_monitor_thread+0xe5 (005bd9d5) 005bd9c9 8935fce08400 mov [mysqld!ut_dbg_null_ptr (0084e0fc)],esi
[19 Dec 2006 21:50]
Valeriy Kravchuk
Please, send the corresponding part of MySQL's error log, as Shane already requested.
[20 Jan 2007 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".
Description: Server crashes while idle. See "How to repeat" for further descriptions. The MySQL version 5.0 Community Server for Windows 5.0.27 GA. The MySQL is running as a service with mysqld.exe crashing. Have a mini dump saved from Microsoft Visual Studio 2005. Since don't have debugging symbols the stack trace doesn't resolve for me. Please see if the .dmp file is useful to you. How to repeat: Setup: 5 InnoDB tables, with a particular table having 63 million rows. 1 Memory table, contains a list of items to insert into the table in question. One of the InnoDB table is getting operated by: 1. Inserting 11K rows of (x bigint, y bigint, primary key (`x`,`y`)), InnoDB engine, in a single transaction through a stored procedure which reads/inserts rows from a temporary table, memory engine. 2. Terminate insertion. 3. Rollback transaction. 4. Stop MySQL service. 5. Restart MySQL service. 6. Do nothing, just wait for some time (disk read/write occuring at 2-3MB/s to the table in question). Then, MySQL crashes, Windows dialog box pops up with the description that the process attempted to access memory address at 0x0. Hit OK to terminate. 7. MySQL service cannot be stopped or terminated at this point. Waiting an additional 30 minutes later the service eventually terminates. 7a. If instead rebooted server, then we'd see the same crash occur again unless the service had terminated after hitting OK to terminate on the Windows dialog box pop-up. 8. Restarting MySQL service is now fine. The log indicates InnoDB recovery from rolled back transaction. This was seen happening once. The previous time the entire machine locked up.