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

Server crashes: double free or corruption

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Open (View Workflow)
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: 10.3.27
    • Fix Version/s: 10.3
    • Labels:
    • Environment:

      Description

      I couldn't reproduce it manually, but it crashes 1-3 times per day, after that 5 days stable, and again. With same settings

      double free or corruption (!prev)
      2020-12-23 21:30:01 0x7fd010c1d700  InnoDB: Assertion failure in file /build/mariadb-10.3-Zg5BW3/mariadb-10.3-10.3.27/storage/innobase/include/ut0lst.h line 334
      InnoDB: Failing assertion: list.count > 0
      InnoDB: We intentionally generate a memory trap.
      InnoDB: Submit a detailed bug report to https://jira.mariadb.org/
      InnoDB: If you get repeated assertion failures or crashes, even
      InnoDB: immediately after the mysqld startup, there may be
      InnoDB: corruption in the InnoDB tablespace. Please refer to
      InnoDB: https://mariadb.com/kb/en/library/innodb-recovery-modes/
      InnoDB: about forcing recovery.
      

      double free or corruption (!prev)
      201217  6:40:01 [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.27-MariaDB-0+deb10u1-log
      key_buffer_size=1317011456
      read_buffer_size=131072
      max_used_connections=50
      max_threads=802
      thread_count=47
      It is possible that mysqld could use up to 
      key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 3049343 K  bytes of memory
      Hope that's ok; if not, decrease some variables in the equation.
       
      Thread pointer: 0x7f11140c89f8
      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 = 0x7f11d01c6dd8 thread_stack 0x30000
      

      Config:

      [mysqld]
      sql-mode=""
      skip-networking=0
      skip-bind-address
      max_connections        = 800
      max_connect_errors = 1000000
      skip-external-locking
       
      character-set-server=utf8
      collation-server=utf8_general_ci
       
      slow_query_log=ON
      slow_query_log_file=/var/log/mysql/mysql-slow.log
      long_query_time=1
       
      # old config:
      key_buffer		= 1256M
      max_allowed_packet	= 320M
      thread_stack		= 192K
      thread_cache_size       = 8
      myisam-recover         = BACKUP
      #table_cache            = 64
      #thread_concurrency     = 10
      #
      # * Query Cache Configuration
      #
      query_cache_limit	= 320M
      query_cache_size        = 640M
      expire_logs_days	= 10
      max_binlog_size         = 100M
      

        Attachments

        1. error.09.01.2021.log
          15 kB
        2. error.12.01.2021.log
          28 kB
        3. error.14.12.log
          13 kB
        4. error.15.12.log
          26 kB
        5. error.17.12.log
          12 kB
        6. error.log
          229 kB

          Issue Links

            Activity

              People

              Assignee:
              marko Marko Mäkelä
              Reporter:
              makhmutov.r RINAT MAKHMUTOV
              Votes:
              2 Vote for this issue
              Watchers:
              5 Start watching this issue

                Dates

                Created:
                Updated:

                  Git Integration

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