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

innodb double free on shutdown after insufficent innodb buffer pool allocation




      About every three days this happens:

      2020-09-30 15:05:16 0 [Note] InnoDB: Using Linux native AIO
      2020-09-30 15:05:16 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
      2020-09-30 15:05:16 0 [Note] InnoDB: Uses event mutexes
      2020-09-30 15:05:16 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
      2020-09-30 15:05:16 0 [Note] InnoDB: Number of pools: 1
      2020-09-30 15:05:16 0 [Note] InnoDB: Using SSE2 crc32 instructions
      2020-09-30 15:05:17 0 [Note] InnoDB: Initializing buffer pool, total size = 128M, instances = 1, chunk size = 128M
      2020-09-30 15:05:17 0 [ERROR] InnoDB: mmap(137297920 bytes) failed; errno 12
      2020-09-30 15:05:17 0 [ERROR] InnoDB: Cannot allocate memory for the buffer pool
      2020-09-30 15:05:17 0 [ERROR] InnoDB: Plugin initialization aborted with error Generic error
      2020-09-30 15:05:17 0 [Note] InnoDB: Starting shutdown...
      double free or corruption (out)
      200930 15:05:17 [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 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.3.17-MariaDB
      It is possible that mysqld could use up to
      key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 467422 K  bytes of memory
      Hope that's ok; if not, decrease some variables in the equation.
      Thread pointer: 0x0
      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 = 0x0 thread_stack 0x49000

      The service crashes and cannot be restarted until I add

      innodb_force_recovery = 1

      to my.cnf AND restart the entire server. What is happening?


        Issue Links



              danblack Daniel Black
              leonheess Leon Heess
              0 Vote for this issue
              2 Start watching this issue



                Git Integration

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