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

Crash (mysqld got signal 11) on UNION + JOIN query

    XMLWordPrintable

Details

    • Bug
    • Status: Closed (View Workflow)
    • Critical
    • Resolution: Fixed
    • 5.5.35
    • 5.5.36
    • None
    • None
    • Freebsd 10, MariaDB 5.5.35

    Description

      following query results in a crash:

      SELECT t1.selected_ID,t2.joined_ID 
      FROM 
      	((SELECT 1 as selected_ID)
      	UNION DISTINCT	
      	(SELECT 2 as selected_ID)) 
      AS t1 
      INNER JOIN joined_table AS t2 ON  t1.selected_ID = t2.joined_ID;

      Below the error log:

      140428 12:00:09 [ERROR] mysqld got signal 11 ;
      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: 5.5.35-MariaDB-log
      key_buffer_size=33554432
      read_buffer_size=131072
      max_used_connections=6
      max_threads=502
      thread_count=6
      It is possible that mysqld could use up to
      key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 1133883 K  bytes of memory
      Hope that's ok; if not, decrease some variables in the equation.
       
      Thread pointer: 0x0x833b74000
      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 = 0x7ffffd757f70 thread_stack 0x48000
      0x9cd52c <my_print_stacktrace+0x2c> at /usr/local/libexec/mysqld
      0x6fe4f3 <handle_fatal_signal+0x213> at /usr/local/libexec/mysqld
       
      Trying to get some variables.
      Some pointers may be invalid and cause the dump to abort.
      Query (0x833c1e018): is an invalid pointer
      Connection ID (thread ID): 2
      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=off

      Attachments

        Activity

          People

            Unassigned Unassigned
            sgtpe Sebastian
            Votes:
            0 Vote for this issue
            Watchers:
            3 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.