MySQL Bugs: #41527: 0xC0000005 Exception in srv_parse_data_file_paths_and

Bug #41527	0xC0000005 Exception in srv_parse_data_file_paths_and_sizes()
Submitted:	17 Dec 2008 1:13	Modified:	17 Dec 2008 12:06
Reporter:	Warren Ashcroft	Email Updates:
Status:	Duplicate	Impact on me:	None
Category:	MySQL Server	Severity:	S2 (Serious)
Version:	5.1.30	OS:	Windows (Windows Server 2003 x86)
Assigned to:		CPU Architecture:	Any
Tags:	006B8853, innodb

Description:
I was in the process of upgrading dozens of MySQL 5.1.24-rc servers to 5.1.30 when one server wouldn't start, MySQL error log said:

081217  0:46:03 - 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=268435456
read_buffer_size=131072
max_used_connections=0
max_threads=2000
threads_connected=0
It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 333592 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...
006B8853    mysqld.exe!srv_parse_data_file_paths_and_sizes()[srv0start.c:211]
006A7E18    mysqld.exe!innobase_init()[ha_innodb.cc:1536]
00442748    mysqld.exe!ha_initialize_handlerton()[handler.cc:434]
00561253    mysqld.exe!plugin_initialize()[sql_plugin.cc:1002]
00565AE5    mysqld.exe!plugin_init()[sql_plugin.cc:1209]
004CE1B4    mysqld.exe!init_server_components()[mysqld.cc:3831]
004CE8C6    mysqld.exe!win_main()[mysqld.cc:4267]
004CECDB    mysqld.exe!mysql_service()[mysqld.cc:4439]
00724593    mysqld.exe!_callthreadstart()[thread.c:293]
0072462C    mysqld.exe!_threadstart()[thread.c:275]
77E64829    kernel32.dll!GetModuleHandleA()
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.

After about an hour of digging around (including trying to start it with a fresh data directory), I tried my.ini variables - in our my.ini (same across all these servers) we have these four variables:

innodb_additional_mem_pool_size=2M
innodb_buffer_pool_size=128M
innodb_file_io_threads=15
innodb_force_recovery=0

I determined that if ANY of these lines exist in my.ini the crash happened but if I removed them then MySQL started fine. I have no idea why this is or why it only happens on this one server, but thought I better report it for the benefit of others (Google 006B8853).

Many Thanks,
Warren Ashcroft

How to repeat:
Unknown

Suggested fix:
Unknown

Thank you for a problem report. It looks like a duplicate of bug #36149. Please, send your entire my.ini and entire error log (compressed).

Hello,
Yes, that bug does look like this one - I did search for other reports but couldn't find any. I no longer have the error log but the full my.ini is as follows:

[mysqld]
port=3306

basedir=C:/MySQL5
tmpdir=C:/MySQL5/temp
datadir=D:/MySQL5/data

long_query_time=10

max_connections=2000
max_user_connections=50
max_allowed_packet=20M

wait_timeout=60
connect_timeout=5
interactive_timeout=1200

secure-auth
log-warnings
skip-host-cache
skip-name-resolve
low-priority-updates

ft_min_word_len=3
default-storage-engine=myisam

innodb_additional_mem_pool_size=2M
innodb_buffer_pool_size=128M
innodb_file_io_threads=15
innodb_force_recovery=0

table_cache=1024
max_tmp_tables=16
sort_buffer_size=4M
key_buffer_size=256M

query_cache_limit=1M
query_cache_size=512M
query_cache_min_res_unit=4096k

Let's assume this is a duplciate of bug #36149 for now.