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

XAMPP Crashed and Crashed

    XMLWordPrintable

Details

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

    Description

      220707 11:40:01 [ERROR] mysqld got exception 0xc0000005 ;
      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.4.24-MariaDB
      key_buffer_size=16777216
      read_buffer_size=262144
      max_used_connections=0
      max_threads=65537
      thread_count=6
      It is possible that mysqld could use up to
      key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 20294 K bytes of memory
      Hope that's ok; if not, decrease some variables in the equation.

      Thread pointer: 0x2243b2e0ae8
      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...
      VCRUNTIME140.dll!memcpy()
      mysqld.exe!parse_user()
      mysqld.exe!parse_user()
      mysqld.exe!?ha_rnd_next@handler@@QEAAHPEAE@Z()
      mysqld.exe!?rr_sequential@@YAHPEAUREAD_RECORD@@@Z()
      mysqld.exe!?acl_init@@YA_N_N@Z()
      mysqld.exe!?acl_reload@@YA_NPEAVTHD@@@Z()
      mysqld.exe!?acl_init@@YA_N_N@Z()
      mysqld.exe!?win_main@@YAHHPEAPEAD@Z()
      mysqld.exe!?mysql_service@@YAXPEAX@Z()
      mysqld.exe!?mysqld_main@@YAHHPEAPEAD@Z()
      mysqld.exe!strxnmov()
      KERNEL32.DLL!BaseThreadInitThunk()
      ntdll.dll!RtlUserThreadStart()

      Trying to get some variables.
      Some pointers may be invalid and cause the dump to abort.
      Query (0x0):
      Connection ID (thread ID): 0
      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=on,table_elimination=on,extended_keys=on,exists_to_in=on,orderby_uses_equalities=on,condition_pushdown_for_derived=on,split_materialized=on,condition_pushdown_for_subquery=on,rowid_filter=on,condition_pushdown_from_having=on

      The manual page at https://mariadb.com/kb/en/how-to-produce-a-full-stack-trace-for-mysqld/ contains
      information that should help you find out what is causing the crash.
      Writing a core file at C:\xampp\mysql\data\
      Minidump written to C:\xampp\mysql\data\mysqld.dmp
      2022-07-07 11:40:03 0 [Note] InnoDB: Buffer pool(s) load completed at 220707 11:40:03
      2022-07-07 11:40:18 0 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
      2022-07-07 11:40:18 0 [Note] InnoDB: Uses event mutexes
      2022-07-07 11:40:18 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
      2022-07-07 11:40:18 0 [Note] InnoDB: Number of pools: 1
      2022-07-07 11:40:18 0 [Note] InnoDB: Using SSE2 crc32 instructions
      2022-07-07 11:40:18 0 [Note] InnoDB: Initializing buffer pool, total size = 16M, instances = 1, chunk size = 16M
      2022-07-07 11:40:18 0 [Note] InnoDB: Completed initialization of buffer pool
      2022-07-07 11:40:18 0 [Note] InnoDB: Starting crash recovery from checkpoint LSN=847590
      2022-07-07 11:40:24 0 [Note] InnoDB: 128 out of 128 rollback segments are active.
      2022-07-07 11:40:24 0 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1"
      2022-07-07 11:40:24 0 [Note] InnoDB: Creating shared tablespace for temporary tables
      2022-07-07 11:40:24 0 [Note] InnoDB: Setting file 'C:\xampp\mysql\data\ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
      2022-07-07 11:40:24 0 [Note] InnoDB: File 'C:\xampp\mysql\data\ibtmp1' size is now 12 MB.
      2022-07-07 11:40:24 0 [Note] InnoDB: Waiting for purge to start
      2022-07-07 11:40:24 0 [Note] InnoDB: 10.4.24 started; log sequence number 847599; transaction id 1098
      2022-07-07 11:40:24 0 [Note] InnoDB: Loading buffer pool(s) from C:\xampp\mysql\data\ib_buffer_pool
      2022-07-07 11:40:24 0 [Note] Plugin 'FEEDBACK' is disabled.
      2022-07-07 11:40:25 0 [Note] Server socket created on IP: '::'.
      2022-07-07 11:40:25 0x49bc InnoDB: Assertion failure in file D:\winx64-packages\build\src\storage\innobase\os\os0file.cc line 6202
      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.
      2022-07-07 11:40:25 0x4024 InnoDB: Assertion failure in file D:\winx64-packages\build\src\storage\innobase\os\os0file.cc line 6202
      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.
      2

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              Emmtech Emmanuel Omotayo
              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.