Uploaded image for project: 'MariaDB Server'
  1. MariaDB Server
  2. MDEV-11221

main.events_restart failed in buildbot (Assertion `share == 0' failed in TDC_element::assert_clean_share)

Details

    • 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/'

      Attachments

        Issue Links

          relates to

          Bug - A problem which impairs or prevents the functions of the product. MDEV-10043 main.events_restart fails sporadically in buildbot (crashes upon shutdown)

          • Major - Major loss of function.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. MDEV-12177 perfschema.threads_mysql fails in buildbot after sequence of tests

          • Major - Major loss of function.
          • Closed

          Task - A task that needs to be done. MDEV-7069 Fix buildbot failures in main server trees

          • Major - Major loss of function.
          • Stalled

          Activity

            Ascending order - Click to sort in descending order
            svoj Sergey Vojtovich added a comment -

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

            svoj Sergey Vojtovich added a comment - Looks similar to MDEV-10043 . Either bad merge or there's extra race in this poor code.
            elenst Elena Stepanova added a comment -

            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 ...

            elenst Elena Stepanova added a comment - 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 ...
            svoj Sergey Vojtovich added a comment -

            serg, please review fix for this bug.

            svoj Sergey Vojtovich added a comment - serg , please review fix for this bug.

            People

              svoj Sergey Vojtovich
              elenst Elena Stepanova
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Git Integration

                  Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.