Bug #24207 | Crash + InnoDB recovery memory overrun during sql-bench | ||
---|---|---|---|
Submitted: | 11 Nov 2006 0:18 | Modified: | 30 Nov 2006 13:21 |
Reporter: | [ name withheld ] | Email Updates: | |
Status: | Duplicate | Impact on me: | |
Category: | MySQL Server: InnoDB storage engine | Severity: | S2 (Serious) |
Version: | 5.1.12-beta | OS: | Windows (Windows Server 2003 R2 x64 Editi) |
Assigned to: | Assigned Account | CPU Architecture: | Any |
Tags: | crash, overrun, windows, x64 |
[11 Nov 2006 0:18]
[ name withheld ]
[11 Nov 2006 0:26]
[ name withheld ]
mysql error log
Attachment: localhost.err (application/octet-stream, text), 5.55 KiB.
[11 Nov 2006 0:27]
[ name withheld ]
output of run-all-tests
Attachment: nohup.out (application/octet-stream, text), 4.03 KiB.
[11 Nov 2006 0:28]
[ name withheld ]
the output of the insert test
Attachment: insert-mysql-CYGWIN_NT_5.2_WOW64_1.5.21(0.156_4_2)_i686 (application/octet-stream, text), 3.86 KiB.
[11 Nov 2006 13:19]
Valeriy Kravchuk
Thank you for a bug report. How much RAM do you have on that machine? What exact command did you use to run sql-bench?
[11 Nov 2006 13:20]
Valeriy Kravchuk
Sorry, missed other commented. Please, answer to question about RAM only.
[11 Nov 2006 16:01]
[ name withheld ]
The machine has 8GB of RAM.
[13 Nov 2006 12:21]
Heikki Tuuri
This is probably a duplicate of http://bugs.mysql.com/bug.php?id=19424, a suspected compiler bug in the 64-bit Windows.
[13 Nov 2006 12:22]
Heikki Tuuri
Can you repeat this with mysqld-debug.exe? It does not contain compiler optimizations. Regards, Heikki
[13 Nov 2006 16:04]
[ name withheld ]
I tried to reproduce with mysqld-debug.exe from 5.1.12, but bug http://bugs.mysql.com/bug.php?id=24267 blocks me from doing so.