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

MariaDB crash in fix_semijoin_strategies_for_picked_join_order

Details

    • Bug
    • Status: Closed (View Workflow)
    • Critical
    • Resolution: Fixed
    • 10.2.8, 5.5(EOL), 10.0(EOL), 10.1(EOL), 10.2(EOL), 10.3(EOL)
    • 10.2.25, 5.5.65, 10.1.41, 10.3.16, 10.4.6
    • Optimizer
    • None
    • Centos 5.7

    Description

      Found this query that crashes latest MariaDB 10.2.8

      # cat query.txt|mysql test       
      ERROR 2013 (HY000) at line 1: Lost connection to MySQL server during query
      

       mysql
      Welcome to the MariaDB monitor.  Commands end with ; or \g.
      Your MariaDB connection id is 8
      Server version: 10.2.8-MariaDB MariaDB Server
      

      Aug 21 19:02:42 uvn-234-24 mysqld: 170821 19:02:42 [ERROR] mysqld got signal 11 ;
      Aug 21 19:02:42 uvn-234-24 mysqld: This could be because you hit a bug. It is also possible that this binary
      Aug 21 19:02:42 uvn-234-24 mysqld: or one of the libraries it was linked against is corrupt, improperly built,
      Aug 21 19:02:42 uvn-234-24 mysqld: or misconfigured. This error can also be caused by malfunctioning hardware.
      Aug 21 19:02:42 uvn-234-24 mysqld: To report this bug, see https://mariadb.com/kb/en/reporting-bugs
      Aug 21 19:02:42 uvn-234-24 mysqld: We will try our best to scrape up some info that will hopefully help
      Aug 21 19:02:42 uvn-234-24 mysqld: diagnose the problem, but since we have already crashed,
      Aug 21 19:02:42 uvn-234-24 mysqld: something is definitely wrong and this may fail.
      Aug 21 19:02:42 uvn-234-24 mysqld: Server version: 10.2.8-MariaDB
      Aug 21 19:02:42 uvn-234-24 mysqld: key_buffer_size=134217728
      Aug 21 19:02:42 uvn-234-24 mysqld: read_buffer_size=131072
      Aug 21 19:02:42 uvn-234-24 mysqld: max_used_connections=3
      Aug 21 19:02:42 uvn-234-24 mysqld: max_threads=153
      Aug 21 19:02:42 uvn-234-24 mysqld: thread_count=9
      Aug 21 19:02:42 uvn-234-24 mysqld: It is possible that mysqld could use up to
      Aug 21 19:02:42 uvn-234-24 mysqld: key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 467215 K  bytes of memory
      Aug 21 19:02:42 uvn-234-24 mysqld: Hope that's ok; if not, decrease some variables in the equation.
      Aug 21 19:02:42 uvn-234-24 mysqld: Thread pointer: 0x7faf21eb99e8
      Aug 21 19:02:42 uvn-234-24 mysqld: Attempting backtrace. You can use the following information to find out
      Aug 21 19:02:42 uvn-234-24 mysqld: where mysqld died. If you see no messages after this, something went
      Aug 21 19:02:42 uvn-234-24 mysqld: terribly wrong...
      Aug 21 19:02:42 uvn-234-24 mysqld: stack_bottom = 0x7faef80f4d70 thread_stack 0x49000
      Aug 21 19:02:42 uvn-234-24 mysqld: /usr/sbin/mysqld(my_print_stacktrace+0x2e)[0x7faf1edf0a7e]
      Aug 21 19:02:42 uvn-234-24 mysqld: /usr/sbin/mysqld(handle_fatal_signal+0x30d)[0x7faf1e836dbd]
      Aug 21 19:02:42 uvn-234-24 mysqld: /lib64/libpthread.so.0(+0xf130)[0x7faf1dd9f130]
      Aug 21 19:02:42 uvn-234-24 mysqld: /usr/sbin/mysqld(_Z45fix_semijoin_strategies_for_picked_join_orderP4JOIN+0x91)[0x7faf1e7a8bf1]
      Aug 21 19:02:42 uvn-234-24 mysqld: /usr/sbin/mysqld(_ZN4JOIN20get_best_combinationEv+0xc0)[0x7faf1e6d84c0]
      Aug 21 19:02:42 uvn-234-24 mysqld: /usr/sbin/mysqld(+0x5239d4)[0x7faf1e6f29d4]
      Aug 21 19:02:42 uvn-234-24 mysqld: /usr/sbin/mysqld(_ZN4JOIN14optimize_innerEv+0x8c0)[0x7faf1e6f8050]
      Aug 21 19:02:42 uvn-234-24 mysqld: mysys/stacktrace.c:268(my_print_stacktrace)[0x7faf1e6fa32f]
      Aug 21 19:02:42 uvn-234-24 mysqld: sql/opt_subselect.cc:3453(fix_semijoin_strategies_for_picked_join_order(JOIN*))[0x7faf1e6fba34]
      Aug 21 19:02:42 uvn-234-24 mysqld: sql/sql_select.cc:8859(JOIN::get_best_combination())[0x7faf1e6fc614]
      Aug 21 19:02:42 uvn-234-24 mysqld: sql/sql_parse.cc:6447(execute_sqlcom_select)[0x7faf1e69f556]
      Aug 21 19:02:42 uvn-234-24 mysqld: sql/sql_parse.cc:3460(mysql_execute_command(THD*))[0x7faf1e6ab9d2]
      Aug 21 19:02:42 uvn-234-24 mysqld: sql/sql_parse.cc:7887(mysql_parse(THD*, char*, unsigned int, Parser_state*, bool, bool))[0x7faf1e6af0ae]
      Aug 21 19:02:42 uvn-234-24 mysqld: sql/sql_parse.cc:1812(dispatch_command(enum_server_command, THD*, char*, unsigned int, bool, bool))[0x7faf1e6b205d]
      Aug 21 19:02:42 uvn-234-24 mysqld: sql/sql_parse.cc:1362(do_command(THD*))[0x7faf1e6b2c69]
      Aug 21 19:02:42 uvn-234-24 mysqld: sql/sql_connect.cc:1354(do_handle_one_connection(CONNECT*))[0x7faf1e7765da]
      Aug 21 19:02:42 uvn-234-24 mysqld: sql/sql_connect.cc:1262(handle_one_connection)[0x7faf1e7766fd]
      Aug 21 19:02:42 uvn-234-24 mysqld: /lib64/libpthread.so.0(+0x7df3)[0x7faf1dd97df3]
      Aug 21 19:02:42 uvn-234-24 mysqld: /lib64/libc.so.6(clone+0x6d)[0x7faf1c3ef1ad]
      Aug 21 19:02:42 uvn-234-24 mysqld: Trying to get some variables.
      Aug 21 19:02:42 uvn-234-24 mysqld: Some pointers may be invalid and cause the dump to abort.
      Aug 21 19:02:42 uvn-234-24 mysqld: Query (0x7faf21f272f0): SELECT f1_user.name,
      

      Attachments

        1. 1mdev13607.test
          161 kB
          Alice Sherepa
        2. query.txt
          138 kB
          Silver Asu
        3. test.dump
          14 kB
          Silver Asu

        Issue Links

          Activity

            People

              igor Igor Babaev (Inactive)
              BB Silver Asu
              Votes:
              0 Vote for this issue
              Watchers:
              7 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.