[MDEV-11221] main.events_restart failed in buildbot (Assertion `share == 0' failed in TDC_element::assert_clean_share) Created: 2016-11-02  Updated: 2017-03-03  Resolved: 2017-03-01

Status: Closed
Project: MariaDB Server
Component/s: Locking, Tests
Affects Version/s: 10.0, 10.1
Fix Version/s: 10.0.30, 10.1.22, 10.2.5

Type: Bug Priority: Major
Reporter: Elena Stepanova Assignee: Sergey Vojtovich
Resolution: Fixed Votes: 0
Labels: None

Issue Links:
Relates
relates to MDEV-10043 main.events_restart fails sporadicall... Closed
relates to MDEV-12177 perfschema.threads_mysql fails in bui... Closed
relates to MDEV-7069 Fix buildbot failures in main server ... Stalled
Sprint: 10.0.30

 Description   

http://buildbot.askmonty.org/buildbot/builders/kvm-fulltest2/builds/6181/steps/test_2/logs/stdio

main.events_restart                      w1 [ fail ]  Found warnings/errors in server log file!
        Test ended at 2016-10-31 13:03:47
line
safe_mutex: Trying to lock unitialized mutex at /home/buildbot/buildbot/build/mariadb-10.1.19/sql/tztime.cc, line 2308
Attempting backtrace. You can use the following information to find out
2016-10-31 13:03:44 2973454144 [ERROR] Plugin 'MyISAM' has ref_count=2 after shutdown.
mysqld: /home/buildbot/buildbot/build/mariadb-10.1.19/sql/table_cache.h:65: void TDC_element::assert_clean_share(): Assertion `share == 0' failed.
^ Found warnings in /mnt/buildbot/build/mariadb-10.1.19/mysql-test/var/1/log/mysqld.1.err
ok
 
 - saving '/mnt/buildbot/build/mariadb-10.1.19/mysql-test/var/1/log/main.events_restart/' to '/mnt/buildbot/build/mariadb-10.1.19/mysql-test/var/log/main.events_restart/'



 Comments   
Comment by Sergey Vojtovich [ 2016-11-02 ]

Looks similar to MDEV-10043. Either bad merge or there's extra race in this poor code.

Comment by Elena Stepanova [ 2016-11-20 ]

Another flavor of failure with the same test – unspecific crash on 10.0 Windows:
http://buildbot.askmonty.org/buildbot/builders/winx64-debug/builds/1581/steps/test/logs/stdio

main.events_restart                      w1 [ fail ]  Found warnings/errors in server log file!
        Test ended at 2016-11-17 13:43:57
line
161117 13:43:51 [ERROR] mysqld got exception 0xc0000005 ;
 
Attempting backtrace. You can use the following information to find out
 
^ Found warnings in D:/winx64-debug/build/mysql-test/var/1/log/mysqld.1.err
ok

Error log isn't helpful:

161117 13:43:51 [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.0.29-MariaDB-debug
key_buffer_size=1048576
read_buffer_size=131072
max_used_connections=1
max_threads=501
thread_count=1
It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 196100 K  bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
 
Thread pointer: 0x0xbedf925c08
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...
161117 13:43:52 [Note] D:/winx64-debug/build/sql//Debug/mysqld.exe (mysqld 10.0.29-MariaDB-debug) starting as process 308 ...

Comment by Sergey Vojtovich [ 2017-02-28 ]

serg, please review fix for this bug.

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