[MDEV-10044] Server crashes after main.shm Created: 2016-05-08  Updated: 2016-05-08  Resolved: 2016-05-08

Status: Closed
Project: MariaDB Server
Component/s: Platform Windows
Affects Version/s: 10.1
Fix Version/s: 10.0.26, 10.1.14

Type: Bug Priority: Major
Reporter: Elena Stepanova Assignee: Vladislav Vaintroub
Resolution: Fixed Votes: 0
Labels: None

Issue Links:
Blocks
blocks MDEV-7069 Fix buildbot failures in main server ... Stalled

 Description   

See
http://buildbot.askmonty.org/buildbot/builders/win32-debug/builds/26/steps/test/logs/stdio
http://buildbot.askmonty.org/buildbot/builders/winx64-packages/builds/88/steps/test/logs/stdio

***Warnings generated in error logs during shutdown after running tests: main.shm
 
160502  9:49:14 [ERROR] mysqld got exception 0xc0000005 ;
Attempting backtrace. You can use the following information to find out

The problem isn't new, we had it mentioned in MDEV-9151. That JIRA item is not about the crash itself, only about MTR not printing the stack trace. The request is valid, but even printing the stack trace wouldn't help much in this case, see the error log:

2016-05-02 10:04:37 7480 [Note] D:/winx64-packages/build/sql//RelWithDebInfo/mysqld.exe: ready for connections.
Version: '10.1.13-MariaDB'  socket: ''  port: 16140  mariadb.org binary distribution
2016-05-02 10:04:39 6040 [Note] D:/winx64-packages/build/sql//RelWithDebInfo/mysqld.exe: Normal shutdown
 
2016-05-02 10:04:39 6040 [Note] D:/winx64-packages/build/sql//RelWithDebInfo/mysqld.exe: Shutdown complete
 
160502 10:04:39 [ERROR] 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.
 
To report this bug, see https://mariadb.com/kb/en/reporting-bugs
 
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.
 
Server version: 10.1.13-MariaDB
read_buffer_size=131072
max_used_connections=2
thread_count=0
Thread pointer: 0x0x1112016788
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...
Got exception in exception handler!



 Comments   
Comment by Vladislav Vaintroub [ 2016-05-08 ]

Fix for this was pushed to 10.0 some time ago here
https://github.com/MariaDB/server/commit/9eba34f08675c31b0796eeb127582be827773070

Generated at Thu Feb 08 07:39:15 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.