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

Buffer overflow when turning off query cache

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Duplicate
    • Affects Version/s: 10.1.32
    • Fix Version/s: N/A
    • Component/s: Query Cache
    • Labels:
    • Environment:
      Ubuntu 16.04LTS

      Description

      MariaDB [(none)]> SHOW GLOBAL VARIABLES LIKE '%query_cache%';
      +------------------------------+----------+
      | Variable_name                | Value    |
      +------------------------------+----------+
      | have_query_cache             | YES      |
      | query_cache_limit            | 262144   |
      | query_cache_min_res_unit     | 4096     |
      | query_cache_size             | 83886080 |
      | query_cache_strip_comments   | OFF      |
      | query_cache_type             | ON       |
      | query_cache_wlock_invalidate | OFF      |
      +------------------------------+----------+
      7 rows in set (0.00 sec)
       
      MariaDB [(none)]> SET GLOBAL query_cache_type = OFF;
      Query OK, 0 rows affected (0.09 sec)

      Almost instantly followed by:

      180424 15:46:34 [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 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.1.32-MariaDB-1~xenial
      key_buffer_size=17179869184
      read_buffer_size=2097152
      max_used_connections=351
      max_threads=352
      thread_count=186
      It is possible that mysqld could use up to 
      key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 19668105 K  bytes of memory
      Hope that's ok; if not, decrease some variables in the equation.
       
      Thread pointer: 0x7f26d0dec008
      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 = 0x7f268b3c3cb8 thread_stack 0x30000
      *** buffer overflow detected ***: /usr/sbin/mysqld terminated
      ======= Backtrace: =========
      /lib/x86_64-linux-gnu/libc.so.6(+0x777e5)[0x7f2b0c2137e5]
      /lib/x86_64-linux-gnu/libc.so.6(__fortify_fail+0x5c)[0x7f2b0c2b515c]
      /lib/x86_64-linux-gnu/libc.so.6(+0x117160)[0x7f2b0c2b3160]
      /lib/x86_64-linux-gnu/libc.so.6(+0x1190a7)[0x7f2b0c2b50a7]
      /usr/sbin/mysqld(my_addr_resolve+0xd4)[0x5574949df634]
      /usr/sbin/mysqld(my_print_stacktrace+0x1e2)[0x5574949c91d2]
      /usr/sbin/mysqld(handle_fatal_signal+0x2f5)[0x5574945101d5]
      /lib/x86_64-linux-gnu/libpthread.so.0(+0x11390)[0x7f2b0cc02390]
      /lib/x86_64-linux-gnu/libpthread.so.0(pthread_rwlock_unlock+0x2c)[0x7f2b0cbfdedc]
      /usr/sbin/mysqld(_ZN11Query_cache11store_queryEP3THDP10TABLE_LIST+0x4a4)[0x5574943420d4]
      /usr/sbin/mysqld(+0x354a68)[0x5574942c2a68]
      /usr/sbin/mysqld(_Z21mysql_execute_commandP3THD+0x71bb)[0x5574943802cb]
      /usr/sbin/mysqld(_Z11mysql_parseP3THDPcjP12Parser_state+0x311)[0x5574943824d1]
      /usr/sbin/mysqld(_Z16dispatch_command19enum_server_commandP3THDPcj+0x25a0)[0x557494385b80]
      /usr/sbin/mysqld(_Z10do_commandP3THD+0x219)[0x557494386439]
      /usr/sbin/mysqld(_Z24do_handle_one_connectionP3THD+0x182)[0x557494454dd2]
      /usr/sbin/mysqld(handle_one_connection+0x40)[0x557494454f70]
      /lib/x86_64-linux-gnu/libpthread.so.0(+0x76ba)[0x7f2b0cbf86ba]
      /lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x7f2b0c2a341d]
      

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              Unassigned Unassigned
              Reporter:
              tgm Martijn
              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.