Bug #70205 | Valgrind: Invalid write of size 4 in memset from init_key_cache | ||
---|---|---|---|
Submitted: | 31 Aug 2013 1:37 | Modified: | 28 Mar 2015 12:27 |
Reporter: | Roel Van de Paar | Email Updates: | |
Status: | Can't repeat | Impact on me: | |
Category: | MySQL Server: MyISAM storage engine | Severity: | S2 (Serious) |
Version: | 5.6 | OS: | Any |
Assigned to: | CPU Architecture: | Any |
[31 Aug 2013 1:37]
Roel Van de Paar
[31 Aug 2013 1:38]
Roel Van de Paar
Adding version
[31 Aug 2013 6:44]
MySQL Verification Team
what was the exact statement to cause this? Looks like some SET global key_buffer_size = ... statement. Had previous ones failed?
[31 Aug 2013 9:22]
MySQL Verification Team
I'd think this could happen if linux is returning a non-null pointer from my_malloc but in fact is out of memory (overcommit?) ?
[31 Aug 2013 15:53]
MySQL Verification Team
would be nice to know how this was triggered. simple random tests here didn't show any problems. also, try trigger crash without using valgrind. last time i checked, it didn't like large malloc unless you recompiled it with increased variables.
[5 Sep 2013 0:02]
Roel Van de Paar
Command used on debug Valgrind instrumented build (ref lp:percona_qa/build_mysql.sh and use the "val" one)
Attachment: cmd619 (application/octet-stream, text), 868 bytes.
[5 Sep 2013 0:03]
Roel Van de Paar
yy file
Attachment: 87.yy (application/octet-stream, text), 1.31 MiB.
[5 Sep 2013 0:03]
Roel Van de Paar
Thanks Shane!
[5 Sep 2013 0:06]
Roel Van de Paar
(Script needs CR before cd /sdd/randgen, bad edit)
[10 Dec 2013 7:43]
Roel Van de Paar
Hi Shane, Any more success?
[10 Mar 2014 7:17]
MySQL Verification Team
Seen this related crash once on a test also (5.6.18) mysqld.exe!unlink_block()[mf_keycache.c:1242] mysqld.exe!reg_requests()[mf_keycache.c:1293] mysqld.exe!flush_key_blocks_int()[mf_keycache.c:3929] mysqld.exe!flush_key_blocks()[mf_keycache.c:4052] mysqld.exe!flush_blocks()[mi_check.c:1923] mysqld.exe!mi_repair_by_sort()[mi_check.c:2546] mysqld.exe!ha_myisam::repair()[ha_myisam.cc:1105] mysqld.exe!ha_myisam::enable_indexes()[ha_myisam.cc:1405] mysqld.exe!ha_myisam::end_bulk_insert()[ha_myisam.cc:1540] mysqld.exe!copy_data_between_tables()[sql_table.cc:8971] mysqld.exe!mysql_alter_table()[sql_table.cc:8440] mysqld.exe!Sql_cmd_alter_table::execute()[sql_alter.cc:313] mysqld.exe!mysql_execute_command()[sql_parse.cc:4937] mysqld.exe!mysql_parse()[sql_parse.cc:6240] mysqld.exe!dispatch_command()[sql_parse.cc:1337] mysqld.exe!do_command()[sql_parse.cc:1042] mysqld.exe!do_handle_one_connection()[sql_connect.cc:982] mysqld.exe!handle_one_connection()[sql_connect.cc:900] mysqld.exe!pthread_start()[my_winthread.c:63] mysqld.exe!_callthreadstartex()[threadex.c:314] mysqld.exe!_threadstartex()[threadex.c:292]
[19 May 2014 2:12]
Roel Van de Paar
Hi Shane, how is this one going? See status is set to analyzing. Thanks
[28 Mar 2015 12:27]
MySQL Verification Team
never seen this particular crash, even after running a full grammar test workload. if it happens again, please try reduce a testcase and see if it crashes outside of valgrind