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

Server crash with Signal 6

    XMLWordPrintable

Details

    • 10.1.8-3, 10.1.8-4

    Description

      If I run this store procedure twice in a row in the same session, the server will crash with Signal 6.

      CREATE DEFINER = 'leo'@'%'
      PROCEDURE PlayGround.procedure2()
      BEGIN
       
        Select 
          (Select Sum(`TestCase`.Revenue) From PlayGround.Anything E           
            Where TestCase.TemplateID not in (Select 1 from PlayGround.Anything where 2=2)
           ) As `ControlRev`
        From 
        (Select  3 as Revenue, 4 as TemplateID) As `TestCase` 
        Group By  TestCase.Revenue, TestCase.TemplateID;
       
      END

      PlayGround.Anything table is an empty table with only one primary key field `ID`, and it doesn't really have to do anything, it could be any table even mysql.slow_log. The content of the SP may look strange, but I was try to simplify my product SP to create a test case.

      Here is the log

      pure virtual method called
      terminate called without an active exception
      150112 11:47:42 [ERROR] mysqld got signal 6 ;
      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 http://kb.askmonty.org/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.15-MariaDB-wsrep-log
      key_buffer_size=524288
      read_buffer_size=131072
      max_used_connections=1
      max_threads=501
      thread_count=11
      It is possible that mysqld could use up to 
      key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 525444581 K  bytes of memory
      Hope that's ok; if not, decrease some variables in the equation.
       
      Thread pointer: 0x0x7f30c3f7c008
      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 = 0x7f316f0efcb0 thread_stack 0x40000
      /usr/sbin/mysqld(my_print_stacktrace+0x2e)[0xbe922e]
      /usr/sbin/mysqld(handle_fatal_signal+0x390)[0x751a10]
      /lib64/libpthread.so.0(+0xf130)[0x7f3974025130]
      /lib64/libc.so.6(gsignal+0x39)[0x7f39727dd5c9]
      /lib64/libc.so.6(abort+0x148)[0x7f39727decd8]
      /lib64/libstdc++.so.6(_ZN9__gnu_cxx27__verbose_terminate_handlerEv+0x165)[0x7f3972ecb9d5]
      /lib64/libstdc++.so.6(+0x5e946)[0x7f3972ec9946]
      /lib64/libstdc++.so.6(+0x5e973)[0x7f3972ec9973]
      /lib64/libstdc++.so.6(+0x5f4df)[0x7f3972eca4df]
      /usr/sbin/mysqld(_ZN10Item_cache5setupEP4Item+0x48)[0x779408]
      /usr/sbin/mysqld(_ZN17Item_in_optimizer8fix_leftEP3THD+0x3e)[0x78b87e]
      /usr/sbin/mysqld(_ZN17Item_in_optimizer10fix_fieldsEP3THDPP4Item+0x18)[0x78bbe8]
      /usr/sbin/mysqld(_ZN9Item_func10fix_fieldsEP3THDPP4Item+0x190)[0x7ace70]
      /usr/sbin/mysqld(_ZN13Item_func_not10fix_fieldsEP3THDPP4Item+0x32e)[0x78681e]
      /usr/sbin/mysqld(_Z11setup_condsP3THDP10TABLE_LISTR4ListIS1_EPP4Item+0x188)[0x590868]
      /usr/sbin/mysqld[0x623087]
      /usr/sbin/mysqld(_ZN30subselect_single_select_engine7prepareEv+0x6d6)[0x7e2b66]
      /usr/sbin/mysqld(_ZN14Item_subselect10fix_fieldsEP3THDPP4Item+0xd5)[0x7e0945]
      /usr/sbin/mysqld(_Z12setup_fieldsP3THDPP4ItemR4ListIS1_E17enum_mark_columnsPS5_b+0x17c)[0x58eaec]
      /usr/sbin/mysqld[0x622fd2]
      /usr/sbin/mysqld(_Z12mysql_selectP3THDPPP4ItemP10TABLE_LISTjR4ListIS1_ES2_jP8st_orderSB_S2_SB_yP13select_resultP18st_select_lex_unitP13st_select_lex+0x8f6)[0x62e656]
      /usr/sbin/mysqld(_Z13handle_selectP3THDP3LEXP13select_resultm+0x27d)[0x62e95d]
      /usr/sbin/mysqld[0x5cdd1e]
      /usr/sbin/mysqld(_Z21mysql_execute_commandP3THD+0x569d)[0x5dc71d]
      /usr/sbin/mysqld(_ZN13sp_instr_stmt9exec_coreEP3THDPj+0x34)[0x86ab44]
      /usr/sbin/mysqld(_ZN13sp_lex_keeper23reset_lex_and_exec_coreEP3THDPjbP8sp_instr+0x80)[0x872000]
      /usr/sbin/mysqld(_ZN13sp_instr_stmt7executeEP3THDPj+0x155)[0x872425]
      /usr/sbin/mysqld(_ZN7sp_head7executeEP3THDb+0x6ac)[0x86f0dc]
      /usr/sbin/mysqld(_ZN7sp_head17execute_procedureEP3THDP4ListI4ItemE+0x694)[0x870704]
      /usr/sbin/mysqld(_Z21mysql_execute_commandP3THD+0x5faf)[0x5dd02f]
      /usr/sbin/mysqld[0x5e0c61]
      /usr/sbin/mysqld(_Z16dispatch_command19enum_server_commandP3THDPcj+0x1ac5)[0x5e2c95]
      /usr/sbin/mysqld(_Z10do_commandP3THD+0x1ba)[0x5e398a]
      /usr/sbin/mysqld(_Z26threadpool_process_requestP3THD+0xc7)[0x6e3d17]
      /usr/sbin/mysqld[0x7246ed]
      /lib64/libpthread.so.0(+0x7df3)[0x7f397401ddf3]
      /lib64/libc.so.6(clone+0x6d)[0x7f397289e01d]
       
      Trying to get some variables.
      Some pointers may be invalid and cause the dump to abort.
      Query (0x7f30c2c56020): is an invalid pointer
      Connection ID (thread ID): 13
      Status: NOT_KILLED
       
      Optimizer switch: index_merge=on,index_merge_union=on,index_merge_sort_union=on,index_merge_intersection=on,index_merge_sort_intersection=off,engine_condition_pushdown=off,index_condition_pushdown=on,derived_merge=on,derived_with_keys=on,firstmatch=on,loosescan=on,materialization=on,in_to_exists=on,semijoin=on,partial_match_rowid_merge=on,partial_match_table_scan=on,subquery_cache=on,mrr=off,mrr_cost_based=off,mrr_sort_keys=off,outer_join_with_cache=on,semijoin_with_cache=on,join_cache_incremental=on,join_cache_hashed=on,join_cache_bka=on,optimize_join_buffer_size=off,table_elimination=on,extended_keys=on,exists_to_in=on
       
      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.
      150112 11:47:42 mysqld_safe Number of processes running now: 0
      150112 11:47:42 mysqld_safe WSREP: not restarting wsrep node automatically
      150112 11:47:42 mysqld_safe mysqld from pid file /mysqlc/conf/mysql.pid ended

      Attachments

        Issue Links

          Activity

            People

              sanja Oleksandr Byelkin
              leomkkwan Leo Kwan
              Votes:
              0 Vote for this issue
              Watchers:
              5 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.