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

Maria crashes in XAMPP

    XMLWordPrintable

Details

    • Bug
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Incomplete
    • 10.4.34
    • N/A
    • None
    • None
    • Win11
      XAMPP

    Description

      2025-06-23 12:54:32 0x8408 InnoDB: Assertion failure in file D:\winx64-packages\build\src\storage\innobase\os\os0file.cc line 6132
      InnoDB: Failing assertion: slot
      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.
      2025-06-23250623 12:54:32 [ERROR] mysqld got exception 0x80000003 ;
      1Sorry, we probably made a mistake, and this is a bug.

      Your assistance in bug reporting will enable us to fix this for the next release.
      To report this bug, see https://mariadb.com/kb/en/reporting-bugs

      2We 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.4.32-MariaDB source revision: c4143f909528e3fab0677a28631d10389354c491
      5key_buffer_size=16777216
      4read_buffer_size=262144
      :max_used_connections=0
      3max_threads=65537
      2thread_count=6
      It is possible that mysqld could use up to
      key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 20304 K bytes of memory
      0Hope that's ok; if not, decrease some variables in the equation.

      xThread pointer: 0x0
      8Attempting backtrace. You can use the following information to find out
      where mysqld died. If you see no messages after this, something went
      terribly wrong...
      404 InnoDB: Assertion failure in file D:\winx64-packages\build\src\storage\innobase\os\os0file.cc line 6132
      InnoDB: Failing assertion: slot
      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.
      2025-06-23 12:54:32 0x3580 InnoDB: Assertion failure i

      Attachments

        Activity

          People

            Unassigned Unassigned
            MrDog Dave Torr
            Votes:
            0 Vote for this issue
            Watchers:
            5 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.