Bug #80581 | rpl_semi_sync_[non_]group_commit_deadlock crash on ASan, debug | ||
---|---|---|---|
Submitted: | 2 Mar 2016 8:03 | Modified: | 4 Mar 2016 9:47 |
Reporter: | Laurynas Biveinis (OCA) | Email Updates: | |
Status: | Verified | Impact on me: | |
Category: | MySQL Server: Replication | Severity: | S1 (Critical) |
Version: | 5.7.11 | OS: | Any |
Assigned to: | CPU Architecture: | Any | |
Tags: | asan, mtr, semisync, valgrind |
[2 Mar 2016 8:03]
Laurynas Biveinis
[2 Mar 2016 8:30]
Laurynas Biveinis
The non-ASan run could be a timeout, not a hang, but in previous passing attempts I see that this testcase completes rather quickly: rpl.rpl_semi_sync_group_commit_deadlock 'mix' w4 [ pass ] 14412 rpl.rpl_semi_sync_group_commit_deadlock 'row' w4 [ pass ] 14045 rpl.rpl_semi_sync_group_commit_deadlock 'stmt' w2 [ pass ] 14144
[2 Mar 2016 8:31]
Laurynas Biveinis
Debug build hangs on Mac (without -DBUILD_VALGRIND=ON CMake option) too.
[2 Mar 2016 8:32]
Laurynas Biveinis
Same stacktrace with ASan on rpl_semi_sync_non_group_commit_deadlock
[2 Mar 2016 8:44]
Laurynas Biveinis
Got one crashing stacktrace with debug: /mtr --debug-server --big-test --parallel=3 rpl_semi_sync_non_group_commit_deadlock ... rpl.rpl_semi_sync_non_group_commit_deadlock 'mix' w3 [ fail ] Test ended at 2016-03-02 10:39:49 CURRENT_TEST: rpl.rpl_semi_sync_non_group_commit_deadlock mysqltest: In included file ./include/stop_dump_threads.inc at line 27: included from ./include/uninstall_semisync.inc at line 18: included from /Users/laurynas/percona/mysql-5.7.11/mysql-test/suite/rpl/t/rpl_semi_sync_non_group_commit_deadlock.test at line 32: At line 26: query 'let $_sdt_dump_thread_id= `SELECT ID FROM INFORMATION_SCHEMA.PROCESSLIST WHERE COMMAND = 'Binlog dump' OR COMMAND = 'Binlog DUMP GTID'`' failed: 2013: Lost connection to MySQL server during query ... 08:39:37 UTC - mysqld got signal 11 ; ... Thread pointer: 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... stack_bottom = 0 thread_stack 0x40000 0 mysqld-debug 0x000000010c6f4c68 my_print_stacktrace + 72 1 mysqld-debug 0x000000010c59ffc2 handle_fatal_signal + 930 2 libsystem_platform.dylib 0x00007fff9b28deaa _sigtramp + 26 3 libsystem_pthread.dylib 0x00007fff9ec7ee7f pthread_rwlock_unlock + 367 4 mysqld-debug 0x000000010cd3cca5 _Z16lf_hash_put_pinsP10st_lf_pins + 21 5 mysqld-debug 0x000000010cd3cabc _Z14destroy_threadP10PFS_thread + 428 6 mysqld-debug 0x000000010cd1831d pfs_delete_current_thread_v1 + 93 7 mysqld-debug 0x000000010c55d40b handle_connection + 635 8 mysqld-debug 0x000000010cd172db pfs_spawn_thread + 411 9 libsystem_pthread.dylib 0x00007fff9ec80c13 _pthread_body + 131 10 libsystem_pthread.dylib 0x00007fff9ec80b90 _pthread_body + 0 11 libsystem_pthread.dylib 0x00007fff9ec7e375 thread_start + 13
[4 Mar 2016 9:47]
MySQL Verification Team
Hello Laurynas, Thank you for the report. Verified as described with 5.7.11 on Mac OSX(LLVM Version 7.0.2(clang-700.1.81)). Thanks, Umesh