2024-01-31 15:31:31 0 [Note] Starting MariaDB 10.4.32-MariaDB source revision c4143f909528e3fab0677a28631d10389354c491 as process 6276
2024-01-31 15:31:31 0 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2024-01-31 15:31:31 0 [Note] InnoDB: Uses event mutexes
2024-01-31 15:31:31 0 [Note] InnoDB: Compressed tables use zlib 1.3
2024-01-31 15:31:31 0 [Note] InnoDB: Number of pools: 1
2024-01-31 15:31:31 0 [Note] InnoDB: Using SSE2 crc32 instructions
2024-01-31 15:31:31 0 [Note] InnoDB: Initializing buffer pool, total size = 16M, instances = 1, chunk size = 16M
2024-01-31 15:31:31 0 [Note] InnoDB: Completed initialization of buffer pool
2024-01-31 15:31:31 0 [Note] InnoDB: Starting crash recovery from checkpoint LSN=300288
2024-01-31 15:31:31 0 [Note] InnoDB: 128 out of 128 rollback segments are active.
2024-01-31 15:31:31 0 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1"
2024-01-31 15:31:31 0 [Note] InnoDB: Creating shared tablespace for temporary tables
2024-01-31 15:31:31 0 [Note] InnoDB: Setting file 'C:\xampp\mysql\data\ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2024-01-31 15:31:31 0 [Note] InnoDB: File 'C:\xampp\mysql\data\ibtmp1' size is now 12 MB.
2024-01-31 15:31:31 0 [Note] InnoDB: Waiting for purge to start
2024-01-31 15:31:31 0 [Note] InnoDB: 10.4.32 started; log sequence number 300297; transaction id 170
2024-01-31 15:31:31 0 [Note] InnoDB: Loading buffer pool(s) from C:\xampp\mysql\data\ib_buffer_pool
2024-01-31 15:31:31 0 [Note] Plugin 'FEEDBACK' is disabled.
2024-01-31 15:31:31 0 [Note] Server socket created on IP: '::'.
2024-01-31 17:00:39 0 [Note] Starting MariaDB 10.4.32-MariaDB source revision c4143f909528e3fab0677a28631d10389354c491 as process 19796
2024-01-31 17:00:39 0 [Note] mysqld.exe: Aria engine: starting recovery
recovered pages: 0% 13% 55% 82% 95% 100% (0.0 seconds); tables to flush: 2 1 0
 (0.0 seconds); 
2024-01-31 17:00:39 0 [Note] mysqld.exe: Aria engine: recovery done
2024-01-31 17:00:39 0 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2024-01-31 17:00:39 0 [Note] InnoDB: Uses event mutexes
2024-01-31 17:00:39 0 [Note] InnoDB: Compressed tables use zlib 1.3
2024-01-31 17:00:39 0 [Note] InnoDB: Number of pools: 1
2024-01-31 17:00:39 0 [Note] InnoDB: Using SSE2 crc32 instructions
2024-01-31 17:00:39 0 [Note] InnoDB: Initializing buffer pool, total size = 16M, instances = 1, chunk size = 16M
2024-01-31 17:00:39 0 [Note] InnoDB: Completed initialization of buffer pool
2024-01-31 17:00:39 0 [Note] InnoDB: Starting crash recovery from checkpoint LSN=6802727
2024-01-31 17:00:39 0 [Note] InnoDB: 128 out of 128 rollback segments are active.
2024-01-31 17:00:39 0 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1"
2024-01-31 17:00:39 0 [Note] InnoDB: Creating shared tablespace for temporary tables
2024-01-31 17:00:39 0 [Note] InnoDB: Setting file 'C:\xampp\mysql\data\ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2024-01-31 17:00:39 0 [Note] InnoDB: File 'C:\xampp\mysql\data\ibtmp1' size is now 12 MB.
2024-01-31 17:00:39 0 [Note] InnoDB: Waiting for purge to start
2024-01-31 17:00:39 0 [Note] InnoDB: 10.4.32 started; log sequence number 6802736; transaction id 4588
2024-01-31 17:00:39 0 [Note] InnoDB: Loading buffer pool(s) from C:\xampp\mysql\data\ib_buffer_pool
2024-01-31 17:00:39 0 [Note] Plugin 'FEEDBACK' is disabled.
2024-01-31 17:00:39 0 [Note] InnoDB: Buffer pool(s) load completed at 240131 17:00:39
2024-01-31 17:00:39 0 [Note] Server socket created on IP: '::'.
2024-02-05 22:38:41 0 [Note] Starting MariaDB 10.4.32-MariaDB source revision c4143f909528e3fab0677a28631d10389354c491 as process 7212
2024-02-05 22:38:41 0 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2024-02-05 22:38:41 0 [Note] InnoDB: Uses event mutexes
2024-02-05 22:38:41 0 [Note] InnoDB: Compressed tables use zlib 1.3
2024-02-05 22:38:41 0 [Note] InnoDB: Number of pools: 1
2024-02-05 22:38:41 0 [Note] InnoDB: Using SSE2 crc32 instructions
2024-02-05 22:38:41 0 [Note] InnoDB: Initializing buffer pool, total size = 16M, instances = 1, chunk size = 16M
2024-02-05 22:38:41 0 [Note] InnoDB: Completed initialization of buffer pool
2024-02-05 22:38:41 0 [Note] InnoDB: Starting crash recovery from checkpoint LSN=20114330
2024-02-05 22:38:42 0 [Note] InnoDB: 128 out of 128 rollback segments are active.
2024-02-05 22:38:42 0 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1"
2024-02-05 22:38:42 0 [Note] InnoDB: Creating shared tablespace for temporary tables
2024-02-05 22:38:42 0 [Note] InnoDB: Setting file 'C:\xampp\mysql\data\ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2024-02-05 22:38:42 0 [Note] InnoDB: File 'C:\xampp\mysql\data\ibtmp1' size is now 12 MB.
2024-02-05 22:38:42 0 [Note] InnoDB: Waiting for purge to start
2024-02-05 22:38:42 0 [Note] InnoDB: 10.4.32 started; log sequence number 20114339; transaction id 24017
2024-02-05 22:38:42 0 [Note] InnoDB: Loading buffer pool(s) from C:\xampp\mysql\data\ib_buffer_pool
2024-02-05 22:38:42 0 [Note] Plugin 'FEEDBACK' is disabled.
2024-02-05 22:38:42 0 [Note] InnoDB: Buffer pool(s) load completed at 240205 22:38:42
2024-02-05 22:38:42 0 [Note] Server socket created on IP: '::'.
2024-02-06 21:18:57 0 [Note] Starting MariaDB 10.4.32-MariaDB source revision c4143f909528e3fab0677a28631d10389354c491 as process 17536
2024-02-06 21:18:57 0 [Note] mysqld.exe: Aria engine: starting recovery
recovered pages: 0% 100% (0.0 seconds); 
2024-02-06 21:18:57 0 [Note] mysqld.exe: Aria engine: recovery done
2024-02-06 21:18:57 0 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2024-02-06 21:18:57 0 [Note] InnoDB: Uses event mutexes
2024-02-06 21:18:57 0 [Note] InnoDB: Compressed tables use zlib 1.3
2024-02-06 21:18:57 0 [Note] InnoDB: Number of pools: 1
2024-02-06 21:18:57 0 [Note] InnoDB: Using SSE2 crc32 instructions
2024-02-06 21:18:57 0 [Note] InnoDB: Initializing buffer pool, total size = 16M, instances = 1, chunk size = 16M
2024-02-06 21:18:57 0 [Note] InnoDB: Completed initialization of buffer pool
2024-02-06 21:18:57 0 [Note] InnoDB: Starting crash recovery from checkpoint LSN=22267148
2024-02-06 21:18:58 0 [Note] InnoDB: 128 out of 128 rollback segments are active.
2024-02-06 21:18:58 0 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1"
2024-02-06 21:18:58 0 [Note] InnoDB: Creating shared tablespace for temporary tables
2024-02-06 21:18:58 0 [Note] InnoDB: Setting file 'C:\xampp\mysql\data\ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2024-02-06 21:18:58 0 [Note] InnoDB: File 'C:\xampp\mysql\data\ibtmp1' size is now 12 MB.
2024-02-06 21:18:58 0 [Note] InnoDB: Waiting for purge to start
2024-02-06 21:18:58 0 [Note] InnoDB: 10.4.32 started; log sequence number 22267157; transaction id 25082
2024-02-06 21:18:58 0 [Note] InnoDB: Loading buffer pool(s) from C:\xampp\mysql\data\ib_buffer_pool
2024-02-06 21:18:58 0 [Note] Plugin 'FEEDBACK' is disabled.
2024-02-06 21:18:58 0 [Note] InnoDB: Buffer pool(s) load completed at 240206 21:18:58
2024-02-06 21:18:58 0 [Note] Server socket created on IP: '::'.
2024-02-13 20:57:24 0 [Note] Starting MariaDB 10.4.32-MariaDB source revision c4143f909528e3fab0677a28631d10389354c491 as process 13832
2024-02-13 20:57:24 0 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2024-02-13 20:57:24 0 [Note] InnoDB: Uses event mutexes
2024-02-13 20:57:24 0 [Note] InnoDB: Compressed tables use zlib 1.3
2024-02-13 20:57:24 0 [Note] InnoDB: Number of pools: 1
2024-02-13 20:57:24 0 [Note] InnoDB: Using SSE2 crc32 instructions
2024-02-13 20:57:24 0 [Note] InnoDB: Initializing buffer pool, total size = 16M, instances = 1, chunk size = 16M
2024-02-13 20:57:24 0 [Note] InnoDB: Completed initialization of buffer pool
2024-02-13 20:57:24 0 [Note] InnoDB: Starting crash recovery from checkpoint LSN=33032303
2024-02-13 20:57:25 0 [Note] InnoDB: 128 out of 128 rollback segments are active.
2024-02-13 20:57:25 0 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1"
2024-02-13 20:57:25 0 [Note] InnoDB: Creating shared tablespace for temporary tables
2024-02-13 20:57:25 0 [Note] InnoDB: Setting file 'C:\xampp\mysql\data\ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2024-02-13 20:57:25 0 [Note] InnoDB: File 'C:\xampp\mysql\data\ibtmp1' size is now 12 MB.
2024-02-13 20:57:25 0 [Note] InnoDB: Waiting for purge to start
2024-02-13 20:57:25 0 [Note] InnoDB: 10.4.32 started; log sequence number 33032312; transaction id 43073
2024-02-13 20:57:25 0 [Note] InnoDB: Loading buffer pool(s) from C:\xampp\mysql\data\ib_buffer_pool
2024-02-13 20:57:25 0 [Note] Plugin 'FEEDBACK' is disabled.
2024-02-13 20:57:25 0 [Note] InnoDB: Buffer pool(s) load completed at 240213 20:57:25
2024-02-13 20:57:25 0 [Note] Server socket created on IP: '::'.
2024-02-21 19:20:06 0 [Note] Starting MariaDB 10.4.32-MariaDB source revision c4143f909528e3fab0677a28631d10389354c491 as process 28552
2024-02-21 19:20:06 0 [Note] mysqld.exe: Aria engine: starting recovery
recovered pages: 0% 100% (0.0 seconds); 
2024-02-21 19:20:06 0 [Note] mysqld.exe: Aria engine: recovery done
2024-02-21 19:20:06 0 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2024-02-21 19:20:06 0 [Note] InnoDB: Uses event mutexes
2024-02-21 19:20:06 0 [Note] InnoDB: Compressed tables use zlib 1.3
2024-02-21 19:20:06 0 [Note] InnoDB: Number of pools: 1
2024-02-21 19:20:06 0 [Note] InnoDB: Using SSE2 crc32 instructions
2024-02-21 19:20:06 0 [Note] InnoDB: Initializing buffer pool, total size = 16M, instances = 1, chunk size = 16M
2024-02-21 19:20:06 0 [Note] InnoDB: Completed initialization of buffer pool
2024-02-21 19:20:06 0 [Note] InnoDB: Starting crash recovery from checkpoint LSN=41621788
2024-02-21 19:20:06 0 [Note] InnoDB: 128 out of 128 rollback segments are active.
2024-02-21 19:20:06 0 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1"
2024-02-21 19:20:06 0 [Note] InnoDB: Creating shared tablespace for temporary tables
2024-02-21 19:20:06 0 [Note] InnoDB: Setting file 'C:\xampp\mysql\data\ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2024-02-21 19:20:06 0 [Note] InnoDB: File 'C:\xampp\mysql\data\ibtmp1' size is now 12 MB.
2024-02-21 19:20:06 0 [Note] InnoDB: Waiting for purge to start
2024-02-21 19:20:07 0 [Note] InnoDB: 10.4.32 started; log sequence number 41621797; transaction id 50630
2024-02-21 19:20:07 0 [Note] InnoDB: Loading buffer pool(s) from C:\xampp\mysql\data\ib_buffer_pool
2024-02-21 19:20:07 0 [Note] Plugin 'FEEDBACK' is disabled.
2024-02-21 19:20:07 0 [Note] InnoDB: Buffer pool(s) load completed at 240221 19:20:07
2024-02-21 19:20:07 0 [Note] Server socket created on IP: '::'.
2024-02-21 19:22:50 0 [Note] Starting MariaDB 10.4.32-MariaDB source revision c4143f909528e3fab0677a28631d10389354c491 as process 29064
2024-02-21 19:22:50 0 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2024-02-21 19:22:50 0 [Note] InnoDB: Uses event mutexes
2024-02-21 19:22:50 0 [Note] InnoDB: Compressed tables use zlib 1.3
2024-02-21 19:22:50 0 [Note] InnoDB: Number of pools: 1
2024-02-21 19:22:50 0 [Note] InnoDB: Using SSE2 crc32 instructions
2024-02-21 19:22:50 0 [Note] InnoDB: Initializing buffer pool, total size = 16M, instances = 1, chunk size = 16M
2024-02-21 19:22:50 0 [Note] InnoDB: Completed initialization of buffer pool
2024-02-21 19:22:50 0 [Note] InnoDB: Starting crash recovery from checkpoint LSN=41621806
2024-02-21 19:22:50 0 [Note] InnoDB: Starting final batch to recover 5 pages from redo log.
2024-02-21 19:22:50 0 [ERROR] [FATAL] InnoDB: Trying to read page number 49153 in space 0, space name innodb_system, which is outside the tablespace bounds. Byte offset 0, len 16384Please check that the configuration matches the InnoDB system tablespace location (ibdata files)
240221 19:22:50 [ERROR] mysqld got exception 0x80000003 ;
Sorry, 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

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.32-MariaDB source revision: c4143f909528e3fab0677a28631d10389354c491
key_buffer_size=16777216
read_buffer_size=262144
max_used_connections=0
max_threads=65537
thread_count=0
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
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...
mysqld.exe!my_parameter_handler()
ucrtbase.dll!raise()
ucrtbase.dll!abort()
mysqld.exe!??$_Construct@$00PEBD@?$basic_string@DU?$char_traits@D@std@@V?$allocator@D@2@@std@@AEAAXQEBD_K@Z()
mysqld.exe!pthread_dummy()
mysqld.exe!?_Forced_rehash@?$_Hash@V?$_Umap_traits@PEAU_iobuf@@PEAXV?$_Uhash_compare@PEAU_iobuf@@U?$hash@PEAU_iobuf@@@std@@U?$equal_to@PEAU_iobuf@@@3@@std@@V?$allocator@U?$pair@QEAU_iobuf@@PEAX@std@@@3@$0A@@std@@@std@@IEAAX_K@Z()
mysqld.exe!?_Forced_rehash@?$_Hash@V?$_Umap_traits@PEAU_iobuf@@PEAXV?$_Uhash_compare@PEAU_iobuf@@U?$hash@PEAU_iobuf@@@std@@U?$equal_to@PEAU_iobuf@@@3@@std@@V?$allocator@U?$pair@QEAU_iobuf@@PEAX@std@@@3@$0A@@std@@@std@@IEAAX_K@Z()
mysqld.exe!pthread_dummy()
mysqld.exe!pthread_dummy()
mysqld.exe!pthread_dummy()
mysqld.exe!pthread_dummy()
mysqld.exe!pthread_dummy()
mysqld.exe!?_Forced_rehash@?$_Hash@V?$_Umap_traits@PEAU_iobuf@@PEAXV?$_Uhash_compare@PEAU_iobuf@@U?$hash@PEAU_iobuf@@@std@@U?$equal_to@PEAU_iobuf@@@3@@std@@V?$allocator@U?$pair@QEAU_iobuf@@PEAX@std@@@3@$0A@@std@@@std@@IEAAX_K@Z()
mysqld.exe!?_Forced_rehash@?$_Hash@V?$_Umap_traits@PEAU_iobuf@@PEAXV?$_Uhash_compare@PEAU_iobuf@@U?$hash@PEAU_iobuf@@@std@@U?$equal_to@PEAU_iobuf@@@3@@std@@V?$allocator@U?$pair@QEAU_iobuf@@PEAX@std@@@3@$0A@@std@@@std@@IEAAX_K@Z()
mysqld.exe!pthread_dummy()
mysqld.exe!pthread_dummy()
mysqld.exe!pthread_dummy()
mysqld.exe!??$_Reallocate_grow_by@V<lambda_1>@?1??append@?$basic_string@DU?$char_traits@D@std@@V?$allocator@D@2@@std@@QEAAAEAV34@QEBD_K@Z@PEBD_K@?$basic_string@DU?$char_traits@D@std@@V?$allocator@D@2@@std@@AEAAAEAV01@_KV<lambda_1>@?1??append@01@QEAAAEAV01@QEBD0@Z@PEBD_K@Z()
mysqld.exe!?ha_initialize_handlerton@@YAHPEAUst_plugin_int@@@Z()
mysqld.exe!?plugin_dl_foreach@@YA_NPEAVTHD@@PEBUst_mysql_const_lex_string@@P6AD0PEAUst_plugin_int@@PEAX@Z3@Z()
mysqld.exe!?plugin_init@@YAHPEAHPEAPEADH@Z()
mysqld.exe!?plugin_init@@YAHPEAHPEAPEADH@Z()
mysqld.exe!?init_net_server_extension@@YAXPEAVTHD@@@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()
The manual page at https://mariadb.com/kb/en/how-to-produce-a-full-stack-trace-for-mariadbd/ 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
2024-02-21 19:23:55 0 [Note] Starting MariaDB 10.4.32-MariaDB source revision c4143f909528e3fab0677a28631d10389354c491 as process 13104
2024-02-21 19:23:55 0 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2024-02-21 19:23:55 0 [Note] InnoDB: Uses event mutexes
2024-02-21 19:23:55 0 [Note] InnoDB: Compressed tables use zlib 1.3
2024-02-21 19:23:55 0 [Note] InnoDB: Number of pools: 1
2024-02-21 19:23:55 0 [Note] InnoDB: Using SSE2 crc32 instructions
2024-02-21 19:23:55 0 [Note] InnoDB: Initializing buffer pool, total size = 16M, instances = 1, chunk size = 16M
2024-02-21 19:23:55 0 [Note] InnoDB: Completed initialization of buffer pool
2024-02-21 19:23:55 0 [Note] InnoDB: Starting crash recovery from checkpoint LSN=41621806
2024-02-21 19:23:55 0 [Note] InnoDB: Starting final batch to recover 5 pages from redo log.
2024-02-21 19:23:55 0 [ERROR] [FATAL] InnoDB: Trying to read page number 49153 in space 0, space name innodb_system, which is outside the tablespace bounds. Byte offset 0, len 16384Please check that the configuration matches the InnoDB system tablespace location (ibdata files)
240221 19:23:55 [ERROR] mysqld got exception 0x80000003 ;
Sorry, 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

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.32-MariaDB source revision: c4143f909528e3fab0677a28631d10389354c491
key_buffer_size=16777216
read_buffer_size=262144
max_used_connections=0
max_threads=65537
thread_count=0
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
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...
mysqld.exe!my_parameter_handler()
ucrtbase.dll!raise()
ucrtbase.dll!abort()
mysqld.exe!??$_Construct@$00PEBD@?$basic_string@DU?$char_traits@D@std@@V?$allocator@D@2@@std@@AEAAXQEBD_K@Z()
mysqld.exe!pthread_dummy()
mysqld.exe!?_Forced_rehash@?$_Hash@V?$_Umap_traits@PEAU_iobuf@@PEAXV?$_Uhash_compare@PEAU_iobuf@@U?$hash@PEAU_iobuf@@@std@@U?$equal_to@PEAU_iobuf@@@3@@std@@V?$allocator@U?$pair@QEAU_iobuf@@PEAX@std@@@3@$0A@@std@@@std@@IEAAX_K@Z()
mysqld.exe!?_Forced_rehash@?$_Hash@V?$_Umap_traits@PEAU_iobuf@@PEAXV?$_Uhash_compare@PEAU_iobuf@@U?$hash@PEAU_iobuf@@@std@@U?$equal_to@PEAU_iobuf@@@3@@std@@V?$allocator@U?$pair@QEAU_iobuf@@PEAX@std@@@3@$0A@@std@@@std@@IEAAX_K@Z()
mysqld.exe!pthread_dummy()
mysqld.exe!pthread_dummy()
mysqld.exe!pthread_dummy()
mysqld.exe!pthread_dummy()
mysqld.exe!pthread_dummy()
mysqld.exe!?_Forced_rehash@?$_Hash@V?$_Umap_traits@PEAU_iobuf@@PEAXV?$_Uhash_compare@PEAU_iobuf@@U?$hash@PEAU_iobuf@@@std@@U?$equal_to@PEAU_iobuf@@@3@@std@@V?$allocator@U?$pair@QEAU_iobuf@@PEAX@std@@@3@$0A@@std@@@std@@IEAAX_K@Z()
mysqld.exe!?_Forced_rehash@?$_Hash@V?$_Umap_traits@PEAU_iobuf@@PEAXV?$_Uhash_compare@PEAU_iobuf@@U?$hash@PEAU_iobuf@@@std@@U?$equal_to@PEAU_iobuf@@@3@@std@@V?$allocator@U?$pair@QEAU_iobuf@@PEAX@std@@@3@$0A@@std@@@std@@IEAAX_K@Z()
mysqld.exe!pthread_dummy()
mysqld.exe!pthread_dummy()
mysqld.exe!pthread_dummy()
mysqld.exe!??$_Reallocate_grow_by@V<lambda_1>@?1??append@?$basic_string@DU?$char_traits@D@std@@V?$allocator@D@2@@std@@QEAAAEAV34@QEBD_K@Z@PEBD_K@?$basic_string@DU?$char_traits@D@std@@V?$allocator@D@2@@std@@AEAAAEAV01@_KV<lambda_1>@?1??append@01@QEAAAEAV01@QEBD0@Z@PEBD_K@Z()
mysqld.exe!?ha_initialize_handlerton@@YAHPEAUst_plugin_int@@@Z()
mysqld.exe!?plugin_dl_foreach@@YA_NPEAVTHD@@PEBUst_mysql_const_lex_string@@P6AD0PEAUst_plugin_int@@PEAX@Z3@Z()
mysqld.exe!?plugin_init@@YAHPEAHPEAPEADH@Z()
mysqld.exe!?plugin_init@@YAHPEAHPEAPEADH@Z()
mysqld.exe!?init_net_server_extension@@YAXPEAVTHD@@@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()
The manual page at https://mariadb.com/kb/en/how-to-produce-a-full-stack-trace-for-mariadbd/ 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
2024-02-21 19:25:06 0 [Note] Starting MariaDB 10.4.32-MariaDB source revision c4143f909528e3fab0677a28631d10389354c491 as process 29148
2024-02-21 19:25:06 0 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2024-02-21 19:25:06 0 [Note] InnoDB: Uses event mutexes
2024-02-21 19:25:06 0 [Note] InnoDB: Compressed tables use zlib 1.3
2024-02-21 19:25:06 0 [Note] InnoDB: Number of pools: 1
2024-02-21 19:25:06 0 [Note] InnoDB: Using SSE2 crc32 instructions
2024-02-21 19:25:06 0 [Note] InnoDB: Initializing buffer pool, total size = 16M, instances = 1, chunk size = 16M
2024-02-21 19:25:06 0 [Note] InnoDB: Completed initialization of buffer pool
2024-02-21 19:25:06 0 [Note] InnoDB: Starting crash recovery from checkpoint LSN=41621806
2024-02-21 19:25:06 0 [Note] InnoDB: Starting final batch to recover 5 pages from redo log.
2024-02-21 19:25:06 0 [ERROR] [FATAL] InnoDB: Trying to read page number 49153 in space 0, space name innodb_system, which is outside the tablespace bounds. Byte offset 0, len 16384Please check that the configuration matches the InnoDB system tablespace location (ibdata files)
240221 19:25:06 [ERROR] mysqld got exception 0x80000003 ;
Sorry, 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

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.32-MariaDB source revision: c4143f909528e3fab0677a28631d10389354c491
key_buffer_size=16777216
read_buffer_size=262144
max_used_connections=0
max_threads=65537
thread_count=0
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
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...
mysqld.exe!my_parameter_handler()
ucrtbase.dll!raise()
ucrtbase.dll!abort()
mysqld.exe!??$_Construct@$00PEBD@?$basic_string@DU?$char_traits@D@std@@V?$allocator@D@2@@std@@AEAAXQEBD_K@Z()
mysqld.exe!pthread_dummy()
mysqld.exe!?_Forced_rehash@?$_Hash@V?$_Umap_traits@PEAU_iobuf@@PEAXV?$_Uhash_compare@PEAU_iobuf@@U?$hash@PEAU_iobuf@@@std@@U?$equal_to@PEAU_iobuf@@@3@@std@@V?$allocator@U?$pair@QEAU_iobuf@@PEAX@std@@@3@$0A@@std@@@std@@IEAAX_K@Z()
mysqld.exe!?_Forced_rehash@?$_Hash@V?$_Umap_traits@PEAU_iobuf@@PEAXV?$_Uhash_compare@PEAU_iobuf@@U?$hash@PEAU_iobuf@@@std@@U?$equal_to@PEAU_iobuf@@@3@@std@@V?$allocator@U?$pair@QEAU_iobuf@@PEAX@std@@@3@$0A@@std@@@std@@IEAAX_K@Z()
mysqld.exe!pthread_dummy()
mysqld.exe!pthread_dummy()
mysqld.exe!pthread_dummy()
mysqld.exe!pthread_dummy()
mysqld.exe!pthread_dummy()
mysqld.exe!?_Forced_rehash@?$_Hash@V?$_Umap_traits@PEAU_iobuf@@PEAXV?$_Uhash_compare@PEAU_iobuf@@U?$hash@PEAU_iobuf@@@std@@U?$equal_to@PEAU_iobuf@@@3@@std@@V?$allocator@U?$pair@QEAU_iobuf@@PEAX@std@@@3@$0A@@std@@@std@@IEAAX_K@Z()
mysqld.exe!?_Forced_rehash@?$_Hash@V?$_Umap_traits@PEAU_iobuf@@PEAXV?$_Uhash_compare@PEAU_iobuf@@U?$hash@PEAU_iobuf@@@std@@U?$equal_to@PEAU_iobuf@@@3@@std@@V?$allocator@U?$pair@QEAU_iobuf@@PEAX@std@@@3@$0A@@std@@@std@@IEAAX_K@Z()
mysqld.exe!pthread_dummy()
mysqld.exe!pthread_dummy()
mysqld.exe!pthread_dummy()
mysqld.exe!??$_Reallocate_grow_by@V<lambda_1>@?1??append@?$basic_string@DU?$char_traits@D@std@@V?$allocator@D@2@@std@@QEAAAEAV34@QEBD_K@Z@PEBD_K@?$basic_string@DU?$char_traits@D@std@@V?$allocator@D@2@@std@@AEAAAEAV01@_KV<lambda_1>@?1??append@01@QEAAAEAV01@QEBD0@Z@PEBD_K@Z()
mysqld.exe!?ha_initialize_handlerton@@YAHPEAUst_plugin_int@@@Z()
mysqld.exe!?plugin_dl_foreach@@YA_NPEAVTHD@@PEBUst_mysql_const_lex_string@@P6AD0PEAUst_plugin_int@@PEAX@Z3@Z()
mysqld.exe!?plugin_init@@YAHPEAHPEAPEADH@Z()
mysqld.exe!?plugin_init@@YAHPEAHPEAPEADH@Z()
mysqld.exe!?init_net_server_extension@@YAXPEAVTHD@@@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()
The manual page at https://mariadb.com/kb/en/how-to-produce-a-full-stack-trace-for-mariadbd/ 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
2024-02-26 19:12:16 0 [Note] Starting MariaDB 10.4.32-MariaDB source revision c4143f909528e3fab0677a28631d10389354c491 as process 6376
2024-02-26 19:12:17 0 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2024-02-26 19:12:17 0 [Note] InnoDB: Uses event mutexes
2024-02-26 19:12:17 0 [Note] InnoDB: Compressed tables use zlib 1.3
2024-02-26 19:12:17 0 [Note] InnoDB: Number of pools: 1
2024-02-26 19:12:17 0 [Note] InnoDB: Using SSE2 crc32 instructions
2024-02-26 19:12:17 0 [Note] InnoDB: Initializing buffer pool, total size = 16M, instances = 1, chunk size = 16M
2024-02-26 19:12:17 0 [Note] InnoDB: Completed initialization of buffer pool
2024-02-26 19:12:17 0 [Note] InnoDB: Starting crash recovery from checkpoint LSN=41621806
2024-02-26 19:12:17 0 [Note] InnoDB: Starting final batch to recover 5 pages from redo log.
2024-02-26 19:12:17 0 [ERROR] [FATAL] InnoDB: Trying to read page number 49153 in space 0, space name innodb_system, which is outside the tablespace bounds. Byte offset 0, len 16384Please check that the configuration matches the InnoDB system tablespace location (ibdata files)
240226 19:12:17 [ERROR] mysqld got exception 0x80000003 ;
Sorry, 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

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.32-MariaDB source revision: c4143f909528e3fab0677a28631d10389354c491
key_buffer_size=16777216
read_buffer_size=262144
max_used_connections=0
max_threads=65537
thread_count=0
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
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...
mysqld.exe!my_parameter_handler()
ucrtbase.dll!raise()
ucrtbase.dll!abort()
mysqld.exe!??$_Construct@$00PEBD@?$basic_string@DU?$char_traits@D@std@@V?$allocator@D@2@@std@@AEAAXQEBD_K@Z()
mysqld.exe!pthread_dummy()
mysqld.exe!?_Forced_rehash@?$_Hash@V?$_Umap_traits@PEAU_iobuf@@PEAXV?$_Uhash_compare@PEAU_iobuf@@U?$hash@PEAU_iobuf@@@std@@U?$equal_to@PEAU_iobuf@@@3@@std@@V?$allocator@U?$pair@QEAU_iobuf@@PEAX@std@@@3@$0A@@std@@@std@@IEAAX_K@Z()
mysqld.exe!?_Forced_rehash@?$_Hash@V?$_Umap_traits@PEAU_iobuf@@PEAXV?$_Uhash_compare@PEAU_iobuf@@U?$hash@PEAU_iobuf@@@std@@U?$equal_to@PEAU_iobuf@@@3@@std@@V?$allocator@U?$pair@QEAU_iobuf@@PEAX@std@@@3@$0A@@std@@@std@@IEAAX_K@Z()
mysqld.exe!pthread_dummy()
mysqld.exe!pthread_dummy()
mysqld.exe!pthread_dummy()
mysqld.exe!pthread_dummy()
mysqld.exe!pthread_dummy()
mysqld.exe!?_Forced_rehash@?$_Hash@V?$_Umap_traits@PEAU_iobuf@@PEAXV?$_Uhash_compare@PEAU_iobuf@@U?$hash@PEAU_iobuf@@@std@@U?$equal_to@PEAU_iobuf@@@3@@std@@V?$allocator@U?$pair@QEAU_iobuf@@PEAX@std@@@3@$0A@@std@@@std@@IEAAX_K@Z()
mysqld.exe!?_Forced_rehash@?$_Hash@V?$_Umap_traits@PEAU_iobuf@@PEAXV?$_Uhash_compare@PEAU_iobuf@@U?$hash@PEAU_iobuf@@@std@@U?$equal_to@PEAU_iobuf@@@3@@std@@V?$allocator@U?$pair@QEAU_iobuf@@PEAX@std@@@3@$0A@@std@@@std@@IEAAX_K@Z()
mysqld.exe!pthread_dummy()
mysqld.exe!pthread_dummy()
mysqld.exe!pthread_dummy()
mysqld.exe!??$_Reallocate_grow_by@V<lambda_1>@?1??append@?$basic_string@DU?$char_traits@D@std@@V?$allocator@D@2@@std@@QEAAAEAV34@QEBD_K@Z@PEBD_K@?$basic_string@DU?$char_traits@D@std@@V?$allocator@D@2@@std@@AEAAAEAV01@_KV<lambda_1>@?1??append@01@QEAAAEAV01@QEBD0@Z@PEBD_K@Z()
mysqld.exe!?ha_initialize_handlerton@@YAHPEAUst_plugin_int@@@Z()
mysqld.exe!?plugin_dl_foreach@@YA_NPEAVTHD@@PEBUst_mysql_const_lex_string@@P6AD0PEAUst_plugin_int@@PEAX@Z3@Z()
mysqld.exe!?plugin_init@@YAHPEAHPEAPEADH@Z()
mysqld.exe!?plugin_init@@YAHPEAHPEAPEADH@Z()
mysqld.exe!?init_net_server_extension@@YAXPEAVTHD@@@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()
The manual page at https://mariadb.com/kb/en/how-to-produce-a-full-stack-trace-for-mariadbd/ 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
2024-02-26 19:16:59 0 [Note] Starting MariaDB 10.4.32-MariaDB source revision c4143f909528e3fab0677a28631d10389354c491 as process 21832
2024-02-26 19:16:59 0 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2024-02-26 19:16:59 0 [Note] InnoDB: Uses event mutexes
2024-02-26 19:16:59 0 [Note] InnoDB: Compressed tables use zlib 1.3
2024-02-26 19:16:59 0 [Note] InnoDB: Number of pools: 1
2024-02-26 19:16:59 0 [Note] InnoDB: Using SSE2 crc32 instructions
2024-02-26 19:16:59 0 [Note] InnoDB: Initializing buffer pool, total size = 16M, instances = 1, chunk size = 16M
2024-02-26 19:16:59 0 [Note] InnoDB: Completed initialization of buffer pool
2024-02-26 19:16:59 0 [Note] InnoDB: Starting crash recovery from checkpoint LSN=41621806
2024-02-26 19:16:59 0 [Note] InnoDB: Starting final batch to recover 5 pages from redo log.
2024-02-26 19:16:59 0 [ERROR] [FATAL] InnoDB: Trying to read page number 49153 in space 0, space name innodb_system, which is outside the tablespace bounds. Byte offset 0, len 16384Please check that the configuration matches the InnoDB system tablespace location (ibdata files)
240226 19:16:59 [ERROR] mysqld got exception 0x80000003 ;
Sorry, 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

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.32-MariaDB source revision: c4143f909528e3fab0677a28631d10389354c491
key_buffer_size=16777216
read_buffer_size=262144
max_used_connections=0
max_threads=65537
thread_count=0
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
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...
mysqld.exe!my_parameter_handler()
ucrtbase.dll!raise()
ucrtbase.dll!abort()
mysqld.exe!??$_Construct@$00PEBD@?$basic_string@DU?$char_traits@D@std@@V?$allocator@D@2@@std@@AEAAXQEBD_K@Z()
mysqld.exe!pthread_dummy()
mysqld.exe!?_Forced_rehash@?$_Hash@V?$_Umap_traits@PEAU_iobuf@@PEAXV?$_Uhash_compare@PEAU_iobuf@@U?$hash@PEAU_iobuf@@@std@@U?$equal_to@PEAU_iobuf@@@3@@std@@V?$allocator@U?$pair@QEAU_iobuf@@PEAX@std@@@3@$0A@@std@@@std@@IEAAX_K@Z()
mysqld.exe!?_Forced_rehash@?$_Hash@V?$_Umap_traits@PEAU_iobuf@@PEAXV?$_Uhash_compare@PEAU_iobuf@@U?$hash@PEAU_iobuf@@@std@@U?$equal_to@PEAU_iobuf@@@3@@std@@V?$allocator@U?$pair@QEAU_iobuf@@PEAX@std@@@3@$0A@@std@@@std@@IEAAX_K@Z()
mysqld.exe!pthread_dummy()
mysqld.exe!pthread_dummy()
mysqld.exe!pthread_dummy()
mysqld.exe!pthread_dummy()
mysqld.exe!pthread_dummy()
mysqld.exe!?_Forced_rehash@?$_Hash@V?$_Umap_traits@PEAU_iobuf@@PEAXV?$_Uhash_compare@PEAU_iobuf@@U?$hash@PEAU_iobuf@@@std@@U?$equal_to@PEAU_iobuf@@@3@@std@@V?$allocator@U?$pair@QEAU_iobuf@@PEAX@std@@@3@$0A@@std@@@std@@IEAAX_K@Z()
mysqld.exe!?_Forced_rehash@?$_Hash@V?$_Umap_traits@PEAU_iobuf@@PEAXV?$_Uhash_compare@PEAU_iobuf@@U?$hash@PEAU_iobuf@@@std@@U?$equal_to@PEAU_iobuf@@@3@@std@@V?$allocator@U?$pair@QEAU_iobuf@@PEAX@std@@@3@$0A@@std@@@std@@IEAAX_K@Z()
mysqld.exe!pthread_dummy()
mysqld.exe!pthread_dummy()
mysqld.exe!pthread_dummy()
mysqld.exe!??$_Reallocate_grow_by@V<lambda_1>@?1??append@?$basic_string@DU?$char_traits@D@std@@V?$allocator@D@2@@std@@QEAAAEAV34@QEBD_K@Z@PEBD_K@?$basic_string@DU?$char_traits@D@std@@V?$allocator@D@2@@std@@AEAAAEAV01@_KV<lambda_1>@?1??append@01@QEAAAEAV01@QEBD0@Z@PEBD_K@Z()
mysqld.exe!?ha_initialize_handlerton@@YAHPEAUst_plugin_int@@@Z()
mysqld.exe!?plugin_dl_foreach@@YA_NPEAVTHD@@PEBUst_mysql_const_lex_string@@P6AD0PEAUst_plugin_int@@PEAX@Z3@Z()
mysqld.exe!?plugin_init@@YAHPEAHPEAPEADH@Z()
mysqld.exe!?plugin_init@@YAHPEAHPEAPEADH@Z()
mysqld.exe!?init_net_server_extension@@YAXPEAVTHD@@@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()
The manual page at https://mariadb.com/kb/en/how-to-produce-a-full-stack-trace-for-mariadbd/ 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
2024-02-26 19:43:25 0 [Note] Starting MariaDB 10.4.32-MariaDB source revision c4143f909528e3fab0677a28631d10389354c491 as process 24956
2024-02-26 19:43:25 0 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2024-02-26 19:43:25 0 [Note] InnoDB: Uses event mutexes
2024-02-26 19:43:25 0 [Note] InnoDB: Compressed tables use zlib 1.3
2024-02-26 19:43:25 0 [Note] InnoDB: Number of pools: 1
2024-02-26 19:43:25 0 [Note] InnoDB: Using SSE2 crc32 instructions
2024-02-26 19:43:25 0 [Note] InnoDB: Initializing buffer pool, total size = 16M, instances = 1, chunk size = 16M
2024-02-26 19:43:25 0 [Note] InnoDB: Completed initialization of buffer pool
2024-02-26 19:43:25 0 [Note] InnoDB: Starting crash recovery from checkpoint LSN=41621806
2024-02-26 19:43:25 0 [Note] InnoDB: Starting final batch to recover 5 pages from redo log.
2024-02-26 19:43:25 0 [ERROR] [FATAL] InnoDB: Trying to read page number 49153 in space 0, space name innodb_system, which is outside the tablespace bounds. Byte offset 0, len 16384Please check that the configuration matches the InnoDB system tablespace location (ibdata files)
240226 19:43:25 [ERROR] mysqld got exception 0x80000003 ;
Sorry, 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

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.32-MariaDB source revision: c4143f909528e3fab0677a28631d10389354c491
key_buffer_size=16777216
read_buffer_size=262144
max_used_connections=0
max_threads=65537
thread_count=0
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
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...
mysqld.exe!my_parameter_handler()
ucrtbase.dll!raise()
ucrtbase.dll!abort()
mysqld.exe!??$_Construct@$00PEBD@?$basic_string@DU?$char_traits@D@std@@V?$allocator@D@2@@std@@AEAAXQEBD_K@Z()
mysqld.exe!pthread_dummy()
mysqld.exe!?_Forced_rehash@?$_Hash@V?$_Umap_traits@PEAU_iobuf@@PEAXV?$_Uhash_compare@PEAU_iobuf@@U?$hash@PEAU_iobuf@@@std@@U?$equal_to@PEAU_iobuf@@@3@@std@@V?$allocator@U?$pair@QEAU_iobuf@@PEAX@std@@@3@$0A@@std@@@std@@IEAAX_K@Z()
mysqld.exe!?_Forced_rehash@?$_Hash@V?$_Umap_traits@PEAU_iobuf@@PEAXV?$_Uhash_compare@PEAU_iobuf@@U?$hash@PEAU_iobuf@@@std@@U?$equal_to@PEAU_iobuf@@@3@@std@@V?$allocator@U?$pair@QEAU_iobuf@@PEAX@std@@@3@$0A@@std@@@std@@IEAAX_K@Z()
mysqld.exe!pthread_dummy()
mysqld.exe!pthread_dummy()
mysqld.exe!pthread_dummy()
mysqld.exe!pthread_dummy()
mysqld.exe!pthread_dummy()
mysqld.exe!?_Forced_rehash@?$_Hash@V?$_Umap_traits@PEAU_iobuf@@PEAXV?$_Uhash_compare@PEAU_iobuf@@U?$hash@PEAU_iobuf@@@std@@U?$equal_to@PEAU_iobuf@@@3@@std@@V?$allocator@U?$pair@QEAU_iobuf@@PEAX@std@@@3@$0A@@std@@@std@@IEAAX_K@Z()
mysqld.exe!?_Forced_rehash@?$_Hash@V?$_Umap_traits@PEAU_iobuf@@PEAXV?$_Uhash_compare@PEAU_iobuf@@U?$hash@PEAU_iobuf@@@std@@U?$equal_to@PEAU_iobuf@@@3@@std@@V?$allocator@U?$pair@QEAU_iobuf@@PEAX@std@@@3@$0A@@std@@@std@@IEAAX_K@Z()
mysqld.exe!pthread_dummy()
mysqld.exe!pthread_dummy()
mysqld.exe!pthread_dummy()
mysqld.exe!??$_Reallocate_grow_by@V<lambda_1>@?1??append@?$basic_string@DU?$char_traits@D@std@@V?$allocator@D@2@@std@@QEAAAEAV34@QEBD_K@Z@PEBD_K@?$basic_string@DU?$char_traits@D@std@@V?$allocator@D@2@@std@@AEAAAEAV01@_KV<lambda_1>@?1??append@01@QEAAAEAV01@QEBD0@Z@PEBD_K@Z()
mysqld.exe!?ha_initialize_handlerton@@YAHPEAUst_plugin_int@@@Z()
mysqld.exe!?plugin_dl_foreach@@YA_NPEAVTHD@@PEBUst_mysql_const_lex_string@@P6AD0PEAUst_plugin_int@@PEAX@Z3@Z()
mysqld.exe!?plugin_init@@YAHPEAHPEAPEADH@Z()
mysqld.exe!?plugin_init@@YAHPEAHPEAPEADH@Z()
mysqld.exe!?init_net_server_extension@@YAXPEAVTHD@@@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()
The manual page at https://mariadb.com/kb/en/how-to-produce-a-full-stack-trace-for-mariadbd/ 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
2024-02-26 19:44:20 0 [Note] Starting MariaDB 10.4.32-MariaDB source revision c4143f909528e3fab0677a28631d10389354c491 as process 18208
2024-02-26 19:44:20 0 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2024-02-26 19:44:20 0 [Note] InnoDB: Uses event mutexes
2024-02-26 19:44:20 0 [Note] InnoDB: Compressed tables use zlib 1.3
2024-02-26 19:44:20 0 [Note] InnoDB: Number of pools: 1
2024-02-26 19:44:20 0 [Note] InnoDB: Using SSE2 crc32 instructions
2024-02-26 19:44:20 0 [Note] InnoDB: Initializing buffer pool, total size = 16M, instances = 1, chunk size = 16M
2024-02-26 19:44:20 0 [Note] InnoDB: Completed initialization of buffer pool
2024-02-26 19:44:20 0 [Note] InnoDB: Starting crash recovery from checkpoint LSN=41621806
2024-02-26 19:44:20 0 [Note] InnoDB: Starting final batch to recover 5 pages from redo log.
2024-02-26 19:44:20 0 [ERROR] [FATAL] InnoDB: Trying to read page number 49153 in space 0, space name innodb_system, which is outside the tablespace bounds. Byte offset 0, len 16384Please check that the configuration matches the InnoDB system tablespace location (ibdata files)
240226 19:44:20 [ERROR] mysqld got exception 0x80000003 ;
Sorry, 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

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.32-MariaDB source revision: c4143f909528e3fab0677a28631d10389354c491
key_buffer_size=16777216
read_buffer_size=262144
max_used_connections=0
max_threads=65537
thread_count=0
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
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...
mysqld.exe!my_parameter_handler()
ucrtbase.dll!raise()
ucrtbase.dll!abort()
mysqld.exe!??$_Construct@$00PEBD@?$basic_string@DU?$char_traits@D@std@@V?$allocator@D@2@@std@@AEAAXQEBD_K@Z()
mysqld.exe!pthread_dummy()
mysqld.exe!?_Forced_rehash@?$_Hash@V?$_Umap_traits@PEAU_iobuf@@PEAXV?$_Uhash_compare@PEAU_iobuf@@U?$hash@PEAU_iobuf@@@std@@U?$equal_to@PEAU_iobuf@@@3@@std@@V?$allocator@U?$pair@QEAU_iobuf@@PEAX@std@@@3@$0A@@std@@@std@@IEAAX_K@Z()
mysqld.exe!?_Forced_rehash@?$_Hash@V?$_Umap_traits@PEAU_iobuf@@PEAXV?$_Uhash_compare@PEAU_iobuf@@U?$hash@PEAU_iobuf@@@std@@U?$equal_to@PEAU_iobuf@@@3@@std@@V?$allocator@U?$pair@QEAU_iobuf@@PEAX@std@@@3@$0A@@std@@@std@@IEAAX_K@Z()
mysqld.exe!pthread_dummy()
mysqld.exe!pthread_dummy()
mysqld.exe!pthread_dummy()
mysqld.exe!pthread_dummy()
mysqld.exe!pthread_dummy()
mysqld.exe!?_Forced_rehash@?$_Hash@V?$_Umap_traits@PEAU_iobuf@@PEAXV?$_Uhash_compare@PEAU_iobuf@@U?$hash@PEAU_iobuf@@@std@@U?$equal_to@PEAU_iobuf@@@3@@std@@V?$allocator@U?$pair@QEAU_iobuf@@PEAX@std@@@3@$0A@@std@@@std@@IEAAX_K@Z()
mysqld.exe!?_Forced_rehash@?$_Hash@V?$_Umap_traits@PEAU_iobuf@@PEAXV?$_Uhash_compare@PEAU_iobuf@@U?$hash@PEAU_iobuf@@@std@@U?$equal_to@PEAU_iobuf@@@3@@std@@V?$allocator@U?$pair@QEAU_iobuf@@PEAX@std@@@3@$0A@@std@@@std@@IEAAX_K@Z()
mysqld.exe!pthread_dummy()
mysqld.exe!pthread_dummy()
mysqld.exe!pthread_dummy()
mysqld.exe!??$_Reallocate_grow_by@V<lambda_1>@?1??append@?$basic_string@DU?$char_traits@D@std@@V?$allocator@D@2@@std@@QEAAAEAV34@QEBD_K@Z@PEBD_K@?$basic_string@DU?$char_traits@D@std@@V?$allocator@D@2@@std@@AEAAAEAV01@_KV<lambda_1>@?1??append@01@QEAAAEAV01@QEBD0@Z@PEBD_K@Z()
mysqld.exe!?ha_initialize_handlerton@@YAHPEAUst_plugin_int@@@Z()
mysqld.exe!?plugin_dl_foreach@@YA_NPEAVTHD@@PEBUst_mysql_const_lex_string@@P6AD0PEAUst_plugin_int@@PEAX@Z3@Z()
mysqld.exe!?plugin_init@@YAHPEAHPEAPEADH@Z()
mysqld.exe!?plugin_init@@YAHPEAHPEAPEADH@Z()
mysqld.exe!?init_net_server_extension@@YAXPEAVTHD@@@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()
The manual page at https://mariadb.com/kb/en/how-to-produce-a-full-stack-trace-for-mariadbd/ 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
2024-02-26 19:44:30 0 [Note] Starting MariaDB 10.4.32-MariaDB source revision c4143f909528e3fab0677a28631d10389354c491 as process 8212
2024-02-26 19:44:30 0 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2024-02-26 19:44:30 0 [Note] InnoDB: Uses event mutexes
2024-02-26 19:44:30 0 [Note] InnoDB: Compressed tables use zlib 1.3
2024-02-26 19:44:30 0 [Note] InnoDB: Number of pools: 1
2024-02-26 19:44:30 0 [Note] InnoDB: Using SSE2 crc32 instructions
2024-02-26 19:44:30 0 [Note] InnoDB: Initializing buffer pool, total size = 16M, instances = 1, chunk size = 16M
2024-02-26 19:44:30 0 [Note] InnoDB: Completed initialization of buffer pool
2024-02-26 19:44:30 0 [Note] InnoDB: Starting crash recovery from checkpoint LSN=41621806
2024-02-26 19:44:30 0 [Note] InnoDB: Starting final batch to recover 5 pages from redo log.
2024-02-26 19:44:30 0 [ERROR] [FATAL] InnoDB: Trying to read page number 49153 in space 0, space name innodb_system, which is outside the tablespace bounds. Byte offset 0, len 16384Please check that the configuration matches the InnoDB system tablespace location (ibdata files)
240226 19:44:30 [ERROR] mysqld got exception 0x80000003 ;
Sorry, 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

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.32-MariaDB source revision: c4143f909528e3fab0677a28631d10389354c491
key_buffer_size=16777216
read_buffer_size=262144
max_used_connections=0
max_threads=65537
thread_count=0
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
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...
mysqld.exe!my_parameter_handler()
ucrtbase.dll!raise()
ucrtbase.dll!abort()
mysqld.exe!??$_Construct@$00PEBD@?$basic_string@DU?$char_traits@D@std@@V?$allocator@D@2@@std@@AEAAXQEBD_K@Z()
mysqld.exe!pthread_dummy()
mysqld.exe!?_Forced_rehash@?$_Hash@V?$_Umap_traits@PEAU_iobuf@@PEAXV?$_Uhash_compare@PEAU_iobuf@@U?$hash@PEAU_iobuf@@@std@@U?$equal_to@PEAU_iobuf@@@3@@std@@V?$allocator@U?$pair@QEAU_iobuf@@PEAX@std@@@3@$0A@@std@@@std@@IEAAX_K@Z()
mysqld.exe!?_Forced_rehash@?$_Hash@V?$_Umap_traits@PEAU_iobuf@@PEAXV?$_Uhash_compare@PEAU_iobuf@@U?$hash@PEAU_iobuf@@@std@@U?$equal_to@PEAU_iobuf@@@3@@std@@V?$allocator@U?$pair@QEAU_iobuf@@PEAX@std@@@3@$0A@@std@@@std@@IEAAX_K@Z()
mysqld.exe!pthread_dummy()
mysqld.exe!pthread_dummy()
mysqld.exe!pthread_dummy()
mysqld.exe!pthread_dummy()
mysqld.exe!pthread_dummy()
mysqld.exe!?_Forced_rehash@?$_Hash@V?$_Umap_traits@PEAU_iobuf@@PEAXV?$_Uhash_compare@PEAU_iobuf@@U?$hash@PEAU_iobuf@@@std@@U?$equal_to@PEAU_iobuf@@@3@@std@@V?$allocator@U?$pair@QEAU_iobuf@@PEAX@std@@@3@$0A@@std@@@std@@IEAAX_K@Z()
mysqld.exe!?_Forced_rehash@?$_Hash@V?$_Umap_traits@PEAU_iobuf@@PEAXV?$_Uhash_compare@PEAU_iobuf@@U?$hash@PEAU_iobuf@@@std@@U?$equal_to@PEAU_iobuf@@@3@@std@@V?$allocator@U?$pair@QEAU_iobuf@@PEAX@std@@@3@$0A@@std@@@std@@IEAAX_K@Z()
mysqld.exe!pthread_dummy()
mysqld.exe!pthread_dummy()
mysqld.exe!pthread_dummy()
mysqld.exe!??$_Reallocate_grow_by@V<lambda_1>@?1??append@?$basic_string@DU?$char_traits@D@std@@V?$allocator@D@2@@std@@QEAAAEAV34@QEBD_K@Z@PEBD_K@?$basic_string@DU?$char_traits@D@std@@V?$allocator@D@2@@std@@AEAAAEAV01@_KV<lambda_1>@?1??append@01@QEAAAEAV01@QEBD0@Z@PEBD_K@Z()
mysqld.exe!?ha_initialize_handlerton@@YAHPEAUst_plugin_int@@@Z()
mysqld.exe!?plugin_dl_foreach@@YA_NPEAVTHD@@PEBUst_mysql_const_lex_string@@P6AD0PEAUst_plugin_int@@PEAX@Z3@Z()
mysqld.exe!?plugin_init@@YAHPEAHPEAPEADH@Z()
mysqld.exe!?plugin_init@@YAHPEAHPEAPEADH@Z()
mysqld.exe!?init_net_server_extension@@YAXPEAVTHD@@@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()
The manual page at https://mariadb.com/kb/en/how-to-produce-a-full-stack-trace-for-mariadbd/ 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
2024-02-26 19:46:23 0 [Note] Starting MariaDB 10.4.32-MariaDB source revision c4143f909528e3fab0677a28631d10389354c491 as process 21112
2024-02-26 19:46:23 0 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2024-02-26 19:46:23 0 [Note] InnoDB: Uses event mutexes
2024-02-26 19:46:23 0 [Note] InnoDB: Compressed tables use zlib 1.3
2024-02-26 19:46:23 0 [Note] InnoDB: Number of pools: 1
2024-02-26 19:46:23 0 [Note] InnoDB: Using SSE2 crc32 instructions
2024-02-26 19:46:23 0 [Note] InnoDB: Initializing buffer pool, total size = 16M, instances = 1, chunk size = 16M
2024-02-26 19:46:23 0 [Note] InnoDB: Completed initialization of buffer pool
2024-02-26 19:46:23 0 [Note] InnoDB: Starting crash recovery from checkpoint LSN=41621806
2024-02-26 19:46:23 0 [Note] InnoDB: Starting final batch to recover 5 pages from redo log.
2024-02-26 19:46:23 0 [ERROR] [FATAL] InnoDB: Trying to read page number 49153 in space 0, space name innodb_system, which is outside the tablespace bounds. Byte offset 0, len 16384Please check that the configuration matches the InnoDB system tablespace location (ibdata files)
240226 19:46:23 [ERROR] mysqld got exception 0x80000003 ;
Sorry, 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

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.32-MariaDB source revision: c4143f909528e3fab0677a28631d10389354c491
key_buffer_size=16777216
read_buffer_size=262144
max_used_connections=0
max_threads=65537
thread_count=0
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
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...
mysqld.exe!my_parameter_handler()
ucrtbase.dll!raise()
ucrtbase.dll!abort()
mysqld.exe!??$_Construct@$00PEBD@?$basic_string@DU?$char_traits@D@std@@V?$allocator@D@2@@std@@AEAAXQEBD_K@Z()
mysqld.exe!pthread_dummy()
mysqld.exe!?_Forced_rehash@?$_Hash@V?$_Umap_traits@PEAU_iobuf@@PEAXV?$_Uhash_compare@PEAU_iobuf@@U?$hash@PEAU_iobuf@@@std@@U?$equal_to@PEAU_iobuf@@@3@@std@@V?$allocator@U?$pair@QEAU_iobuf@@PEAX@std@@@3@$0A@@std@@@std@@IEAAX_K@Z()
mysqld.exe!?_Forced_rehash@?$_Hash@V?$_Umap_traits@PEAU_iobuf@@PEAXV?$_Uhash_compare@PEAU_iobuf@@U?$hash@PEAU_iobuf@@@std@@U?$equal_to@PEAU_iobuf@@@3@@std@@V?$allocator@U?$pair@QEAU_iobuf@@PEAX@std@@@3@$0A@@std@@@std@@IEAAX_K@Z()
mysqld.exe!pthread_dummy()
mysqld.exe!pthread_dummy()
mysqld.exe!pthread_dummy()
mysqld.exe!pthread_dummy()
mysqld.exe!pthread_dummy()
mysqld.exe!?_Forced_rehash@?$_Hash@V?$_Umap_traits@PEAU_iobuf@@PEAXV?$_Uhash_compare@PEAU_iobuf@@U?$hash@PEAU_iobuf@@@std@@U?$equal_to@PEAU_iobuf@@@3@@std@@V?$allocator@U?$pair@QEAU_iobuf@@PEAX@std@@@3@$0A@@std@@@std@@IEAAX_K@Z()
mysqld.exe!?_Forced_rehash@?$_Hash@V?$_Umap_traits@PEAU_iobuf@@PEAXV?$_Uhash_compare@PEAU_iobuf@@U?$hash@PEAU_iobuf@@@std@@U?$equal_to@PEAU_iobuf@@@3@@std@@V?$allocator@U?$pair@QEAU_iobuf@@PEAX@std@@@3@$0A@@std@@@std@@IEAAX_K@Z()
mysqld.exe!pthread_dummy()
mysqld.exe!pthread_dummy()
mysqld.exe!pthread_dummy()
mysqld.exe!??$_Reallocate_grow_by@V<lambda_1>@?1??append@?$basic_string@DU?$char_traits@D@std@@V?$allocator@D@2@@std@@QEAAAEAV34@QEBD_K@Z@PEBD_K@?$basic_string@DU?$char_traits@D@std@@V?$allocator@D@2@@std@@AEAAAEAV01@_KV<lambda_1>@?1??append@01@QEAAAEAV01@QEBD0@Z@PEBD_K@Z()
mysqld.exe!?ha_initialize_handlerton@@YAHPEAUst_plugin_int@@@Z()
mysqld.exe!?plugin_dl_foreach@@YA_NPEAVTHD@@PEBUst_mysql_const_lex_string@@P6AD0PEAUst_plugin_int@@PEAX@Z3@Z()
mysqld.exe!?plugin_init@@YAHPEAHPEAPEADH@Z()
mysqld.exe!?plugin_init@@YAHPEAHPEAPEADH@Z()
mysqld.exe!?init_net_server_extension@@YAXPEAVTHD@@@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()
The manual page at https://mariadb.com/kb/en/how-to-produce-a-full-stack-trace-for-mariadbd/ 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
2024-02-26 19:47:34 0 [Note] Starting MariaDB 10.4.32-MariaDB source revision c4143f909528e3fab0677a28631d10389354c491 as process 18028
2024-02-26 19:47:34 0 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2024-02-26 19:47:34 0 [Note] InnoDB: Uses event mutexes
2024-02-26 19:47:34 0 [Note] InnoDB: Compressed tables use zlib 1.3
2024-02-26 19:47:34 0 [Note] InnoDB: Number of pools: 1
2024-02-26 19:47:34 0 [Note] InnoDB: Using SSE2 crc32 instructions
2024-02-26 19:47:34 0 [Note] InnoDB: Initializing buffer pool, total size = 16M, instances = 1, chunk size = 16M
2024-02-26 19:47:34 0 [Note] InnoDB: Completed initialization of buffer pool
2024-02-26 19:47:34 0 [Note] InnoDB: Starting crash recovery from checkpoint LSN=41621806
2024-02-26 19:47:34 0 [Note] InnoDB: Starting final batch to recover 5 pages from redo log.
2024-02-26 19:47:34 0 [ERROR] [FATAL] InnoDB: Trying to read page number 49153 in space 0, space name innodb_system, which is outside the tablespace bounds. Byte offset 0, len 16384Please check that the configuration matches the InnoDB system tablespace location (ibdata files)
240226 19:47:34 [ERROR] mysqld got exception 0x80000003 ;
Sorry, 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

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.32-MariaDB source revision: c4143f909528e3fab0677a28631d10389354c491
key_buffer_size=16777216
read_buffer_size=262144
max_used_connections=0
max_threads=65537
thread_count=0
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
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...
mysqld.exe!my_parameter_handler()
ucrtbase.dll!raise()
ucrtbase.dll!abort()
mysqld.exe!??$_Construct@$00PEBD@?$basic_string@DU?$char_traits@D@std@@V?$allocator@D@2@@std@@AEAAXQEBD_K@Z()
mysqld.exe!pthread_dummy()
mysqld.exe!?_Forced_rehash@?$_Hash@V?$_Umap_traits@PEAU_iobuf@@PEAXV?$_Uhash_compare@PEAU_iobuf@@U?$hash@PEAU_iobuf@@@std@@U?$equal_to@PEAU_iobuf@@@3@@std@@V?$allocator@U?$pair@QEAU_iobuf@@PEAX@std@@@3@$0A@@std@@@std@@IEAAX_K@Z()
mysqld.exe!?_Forced_rehash@?$_Hash@V?$_Umap_traits@PEAU_iobuf@@PEAXV?$_Uhash_compare@PEAU_iobuf@@U?$hash@PEAU_iobuf@@@std@@U?$equal_to@PEAU_iobuf@@@3@@std@@V?$allocator@U?$pair@QEAU_iobuf@@PEAX@std@@@3@$0A@@std@@@std@@IEAAX_K@Z()
mysqld.exe!pthread_dummy()
mysqld.exe!pthread_dummy()
mysqld.exe!pthread_dummy()
mysqld.exe!pthread_dummy()
mysqld.exe!pthread_dummy()
mysqld.exe!?_Forced_rehash@?$_Hash@V?$_Umap_traits@PEAU_iobuf@@PEAXV?$_Uhash_compare@PEAU_iobuf@@U?$hash@PEAU_iobuf@@@std@@U?$equal_to@PEAU_iobuf@@@3@@std@@V?$allocator@U?$pair@QEAU_iobuf@@PEAX@std@@@3@$0A@@std@@@std@@IEAAX_K@Z()
mysqld.exe!?_Forced_rehash@?$_Hash@V?$_Umap_traits@PEAU_iobuf@@PEAXV?$_Uhash_compare@PEAU_iobuf@@U?$hash@PEAU_iobuf@@@std@@U?$equal_to@PEAU_iobuf@@@3@@std@@V?$allocator@U?$pair@QEAU_iobuf@@PEAX@std@@@3@$0A@@std@@@std@@IEAAX_K@Z()
mysqld.exe!pthread_dummy()
mysqld.exe!pthread_dummy()
mysqld.exe!pthread_dummy()
mysqld.exe!??$_Reallocate_grow_by@V<lambda_1>@?1??append@?$basic_string@DU?$char_traits@D@std@@V?$allocator@D@2@@std@@QEAAAEAV34@QEBD_K@Z@PEBD_K@?$basic_string@DU?$char_traits@D@std@@V?$allocator@D@2@@std@@AEAAAEAV01@_KV<lambda_1>@?1??append@01@QEAAAEAV01@QEBD0@Z@PEBD_K@Z()
mysqld.exe!?ha_initialize_handlerton@@YAHPEAUst_plugin_int@@@Z()
mysqld.exe!?plugin_dl_foreach@@YA_NPEAVTHD@@PEBUst_mysql_const_lex_string@@P6AD0PEAUst_plugin_int@@PEAX@Z3@Z()
mysqld.exe!?plugin_init@@YAHPEAHPEAPEADH@Z()
mysqld.exe!?plugin_init@@YAHPEAHPEAPEADH@Z()
mysqld.exe!?init_net_server_extension@@YAXPEAVTHD@@@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()
The manual page at https://mariadb.com/kb/en/how-to-produce-a-full-stack-trace-for-mariadbd/ 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
2024-02-27 20:41:08 0 [Note] Starting MariaDB 10.4.32-MariaDB source revision c4143f909528e3fab0677a28631d10389354c491 as process 9532
2024-02-27 20:41:08 0 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2024-02-27 20:41:08 0 [Note] InnoDB: Uses event mutexes
2024-02-27 20:41:08 0 [Note] InnoDB: Compressed tables use zlib 1.3
2024-02-27 20:41:08 0 [Note] InnoDB: Number of pools: 1
2024-02-27 20:41:08 0 [Note] InnoDB: Using SSE2 crc32 instructions
2024-02-27 20:41:08 0 [Note] InnoDB: Initializing buffer pool, total size = 16M, instances = 1, chunk size = 16M
2024-02-27 20:41:08 0 [Note] InnoDB: Completed initialization of buffer pool
2024-02-27 20:41:08 0 [Note] InnoDB: Starting crash recovery from checkpoint LSN=41621806
2024-02-27 20:41:08 0 [Note] InnoDB: Starting final batch to recover 5 pages from redo log.
2024-02-27 20:41:08 0 [ERROR] [FATAL] InnoDB: Trying to read page number 49153 in space 0, space name innodb_system, which is outside the tablespace bounds. Byte offset 0, len 16384Please check that the configuration matches the InnoDB system tablespace location (ibdata files)
240227 20:41:08 [ERROR] mysqld got exception 0x80000003 ;
Sorry, 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

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.32-MariaDB source revision: c4143f909528e3fab0677a28631d10389354c491
key_buffer_size=16777216
read_buffer_size=262144
max_used_connections=0
max_threads=65537
thread_count=0
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
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...
mysqld.exe!my_parameter_handler()
ucrtbase.dll!raise()
ucrtbase.dll!abort()
mysqld.exe!??$_Construct@$00PEBD@?$basic_string@DU?$char_traits@D@std@@V?$allocator@D@2@@std@@AEAAXQEBD_K@Z()
mysqld.exe!pthread_dummy()
mysqld.exe!?_Forced_rehash@?$_Hash@V?$_Umap_traits@PEAU_iobuf@@PEAXV?$_Uhash_compare@PEAU_iobuf@@U?$hash@PEAU_iobuf@@@std@@U?$equal_to@PEAU_iobuf@@@3@@std@@V?$allocator@U?$pair@QEAU_iobuf@@PEAX@std@@@3@$0A@@std@@@std@@IEAAX_K@Z()
mysqld.exe!?_Forced_rehash@?$_Hash@V?$_Umap_traits@PEAU_iobuf@@PEAXV?$_Uhash_compare@PEAU_iobuf@@U?$hash@PEAU_iobuf@@@std@@U?$equal_to@PEAU_iobuf@@@3@@std@@V?$allocator@U?$pair@QEAU_iobuf@@PEAX@std@@@3@$0A@@std@@@std@@IEAAX_K@Z()
mysqld.exe!pthread_dummy()
mysqld.exe!pthread_dummy()
mysqld.exe!pthread_dummy()
mysqld.exe!pthread_dummy()
mysqld.exe!pthread_dummy()
mysqld.exe!?_Forced_rehash@?$_Hash@V?$_Umap_traits@PEAU_iobuf@@PEAXV?$_Uhash_compare@PEAU_iobuf@@U?$hash@PEAU_iobuf@@@std@@U?$equal_to@PEAU_iobuf@@@3@@std@@V?$allocator@U?$pair@QEAU_iobuf@@PEAX@std@@@3@$0A@@std@@@std@@IEAAX_K@Z()
mysqld.exe!?_Forced_rehash@?$_Hash@V?$_Umap_traits@PEAU_iobuf@@PEAXV?$_Uhash_compare@PEAU_iobuf@@U?$hash@PEAU_iobuf@@@std@@U?$equal_to@PEAU_iobuf@@@3@@std@@V?$allocator@U?$pair@QEAU_iobuf@@PEAX@std@@@3@$0A@@std@@@std@@IEAAX_K@Z()
mysqld.exe!pthread_dummy()
mysqld.exe!pthread_dummy()
mysqld.exe!pthread_dummy()
mysqld.exe!??$_Reallocate_grow_by@V<lambda_1>@?1??append@?$basic_string@DU?$char_traits@D@std@@V?$allocator@D@2@@std@@QEAAAEAV34@QEBD_K@Z@PEBD_K@?$basic_string@DU?$char_traits@D@std@@V?$allocator@D@2@@std@@AEAAAEAV01@_KV<lambda_1>@?1??append@01@QEAAAEAV01@QEBD0@Z@PEBD_K@Z()
mysqld.exe!?ha_initialize_handlerton@@YAHPEAUst_plugin_int@@@Z()
mysqld.exe!?plugin_dl_foreach@@YA_NPEAVTHD@@PEBUst_mysql_const_lex_string@@P6AD0PEAUst_plugin_int@@PEAX@Z3@Z()
mysqld.exe!?plugin_init@@YAHPEAHPEAPEADH@Z()
mysqld.exe!?plugin_init@@YAHPEAHPEAPEADH@Z()
mysqld.exe!?init_net_server_extension@@YAXPEAVTHD@@@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()
The manual page at https://mariadb.com/kb/en/how-to-produce-a-full-stack-trace-for-mariadbd/ 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
2024-03-01 13:51:23 0 [Note] Starting MariaDB 10.4.32-MariaDB source revision c4143f909528e3fab0677a28631d10389354c491 as process 7900
2024-03-01 13:51:23 0 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2024-03-01 13:51:23 0 [Note] InnoDB: Uses event mutexes
2024-03-01 13:51:23 0 [Note] InnoDB: Compressed tables use zlib 1.3
2024-03-01 13:51:23 0 [Note] InnoDB: Number of pools: 1
2024-03-01 13:51:23 0 [Note] InnoDB: Using SSE2 crc32 instructions
2024-03-01 13:51:23 0 [Note] InnoDB: Initializing buffer pool, total size = 16M, instances = 1, chunk size = 16M
2024-03-01 13:51:23 0 [Note] InnoDB: Completed initialization of buffer pool
2024-03-01 13:51:23 0 [Note] InnoDB: Starting crash recovery from checkpoint LSN=41621806
2024-03-01 13:51:23 0 [Note] InnoDB: Starting final batch to recover 5 pages from redo log.
2024-03-01 13:51:23 0 [ERROR] [FATAL] InnoDB: Trying to read page number 49153 in space 0, space name innodb_system, which is outside the tablespace bounds. Byte offset 0, len 16384Please check that the configuration matches the InnoDB system tablespace location (ibdata files)
240301 13:51:23 [ERROR] mysqld got exception 0x80000003 ;
Sorry, 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

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.32-MariaDB source revision: c4143f909528e3fab0677a28631d10389354c491
key_buffer_size=16777216
read_buffer_size=262144
max_used_connections=0
max_threads=65537
thread_count=0
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
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...
mysqld.exe!my_parameter_handler()
ucrtbase.dll!raise()
ucrtbase.dll!abort()
mysqld.exe!??$_Construct@$00PEBD@?$basic_string@DU?$char_traits@D@std@@V?$allocator@D@2@@std@@AEAAXQEBD_K@Z()
mysqld.exe!pthread_dummy()
mysqld.exe!?_Forced_rehash@?$_Hash@V?$_Umap_traits@PEAU_iobuf@@PEAXV?$_Uhash_compare@PEAU_iobuf@@U?$hash@PEAU_iobuf@@@std@@U?$equal_to@PEAU_iobuf@@@3@@std@@V?$allocator@U?$pair@QEAU_iobuf@@PEAX@std@@@3@$0A@@std@@@std@@IEAAX_K@Z()
mysqld.exe!?_Forced_rehash@?$_Hash@V?$_Umap_traits@PEAU_iobuf@@PEAXV?$_Uhash_compare@PEAU_iobuf@@U?$hash@PEAU_iobuf@@@std@@U?$equal_to@PEAU_iobuf@@@3@@std@@V?$allocator@U?$pair@QEAU_iobuf@@PEAX@std@@@3@$0A@@std@@@std@@IEAAX_K@Z()
mysqld.exe!pthread_dummy()
mysqld.exe!pthread_dummy()
mysqld.exe!pthread_dummy()
mysqld.exe!pthread_dummy()
mysqld.exe!pthread_dummy()
mysqld.exe!?_Forced_rehash@?$_Hash@V?$_Umap_traits@PEAU_iobuf@@PEAXV?$_Uhash_compare@PEAU_iobuf@@U?$hash@PEAU_iobuf@@@std@@U?$equal_to@PEAU_iobuf@@@3@@std@@V?$allocator@U?$pair@QEAU_iobuf@@PEAX@std@@@3@$0A@@std@@@std@@IEAAX_K@Z()
mysqld.exe!?_Forced_rehash@?$_Hash@V?$_Umap_traits@PEAU_iobuf@@PEAXV?$_Uhash_compare@PEAU_iobuf@@U?$hash@PEAU_iobuf@@@std@@U?$equal_to@PEAU_iobuf@@@3@@std@@V?$allocator@U?$pair@QEAU_iobuf@@PEAX@std@@@3@$0A@@std@@@std@@IEAAX_K@Z()
mysqld.exe!pthread_dummy()
mysqld.exe!pthread_dummy()
mysqld.exe!pthread_dummy()
mysqld.exe!??$_Reallocate_grow_by@V<lambda_1>@?1??append@?$basic_string@DU?$char_traits@D@std@@V?$allocator@D@2@@std@@QEAAAEAV34@QEBD_K@Z@PEBD_K@?$basic_string@DU?$char_traits@D@std@@V?$allocator@D@2@@std@@AEAAAEAV01@_KV<lambda_1>@?1??append@01@QEAAAEAV01@QEBD0@Z@PEBD_K@Z()
mysqld.exe!?ha_initialize_handlerton@@YAHPEAUst_plugin_int@@@Z()
mysqld.exe!?plugin_dl_foreach@@YA_NPEAVTHD@@PEBUst_mysql_const_lex_string@@P6AD0PEAUst_plugin_int@@PEAX@Z3@Z()
mysqld.exe!?plugin_init@@YAHPEAHPEAPEADH@Z()
mysqld.exe!?plugin_init@@YAHPEAHPEAPEADH@Z()
mysqld.exe!?init_net_server_extension@@YAXPEAVTHD@@@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()
The manual page at https://mariadb.com/kb/en/how-to-produce-a-full-stack-trace-for-mariadbd/ 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
2024-03-06 12:54:31 0 [Note] Starting MariaDB 10.4.32-MariaDB source revision c4143f909528e3fab0677a28631d10389354c491 as process 14172
2024-03-06 12:54:31 0 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2024-03-06 12:54:31 0 [Note] InnoDB: Uses event mutexes
2024-03-06 12:54:31 0 [Note] InnoDB: Compressed tables use zlib 1.3
2024-03-06 12:54:31 0 [Note] InnoDB: Number of pools: 1
2024-03-06 12:54:31 0 [Note] InnoDB: Using SSE2 crc32 instructions
2024-03-06 12:54:31 0 [Note] InnoDB: Initializing buffer pool, total size = 16M, instances = 1, chunk size = 16M
2024-03-06 12:54:31 0 [Note] InnoDB: Completed initialization of buffer pool
2024-03-06 12:54:31 0 [Note] InnoDB: Starting crash recovery from checkpoint LSN=41621806
2024-03-06 12:54:31 0 [Note] InnoDB: Starting final batch to recover 5 pages from redo log.
2024-03-06 12:54:31 0 [ERROR] [FATAL] InnoDB: Trying to read page number 49153 in space 0, space name innodb_system, which is outside the tablespace bounds. Byte offset 0, len 16384Please check that the configuration matches the InnoDB system tablespace location (ibdata files)
240306 12:54:31 [ERROR] mysqld got exception 0x80000003 ;
Sorry, 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

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.32-MariaDB source revision: c4143f909528e3fab0677a28631d10389354c491
key_buffer_size=16777216
read_buffer_size=262144
max_used_connections=0
max_threads=65537
thread_count=0
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
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...
mysqld.exe!my_parameter_handler()
ucrtbase.dll!raise()
ucrtbase.dll!abort()
mysqld.exe!??$_Construct@$00PEBD@?$basic_string@DU?$char_traits@D@std@@V?$allocator@D@2@@std@@AEAAXQEBD_K@Z()
mysqld.exe!pthread_dummy()
mysqld.exe!?_Forced_rehash@?$_Hash@V?$_Umap_traits@PEAU_iobuf@@PEAXV?$_Uhash_compare@PEAU_iobuf@@U?$hash@PEAU_iobuf@@@std@@U?$equal_to@PEAU_iobuf@@@3@@std@@V?$allocator@U?$pair@QEAU_iobuf@@PEAX@std@@@3@$0A@@std@@@std@@IEAAX_K@Z()
mysqld.exe!?_Forced_rehash@?$_Hash@V?$_Umap_traits@PEAU_iobuf@@PEAXV?$_Uhash_compare@PEAU_iobuf@@U?$hash@PEAU_iobuf@@@std@@U?$equal_to@PEAU_iobuf@@@3@@std@@V?$allocator@U?$pair@QEAU_iobuf@@PEAX@std@@@3@$0A@@std@@@std@@IEAAX_K@Z()
mysqld.exe!pthread_dummy()
mysqld.exe!pthread_dummy()
mysqld.exe!pthread_dummy()
mysqld.exe!pthread_dummy()
mysqld.exe!pthread_dummy()
mysqld.exe!?_Forced_rehash@?$_Hash@V?$_Umap_traits@PEAU_iobuf@@PEAXV?$_Uhash_compare@PEAU_iobuf@@U?$hash@PEAU_iobuf@@@std@@U?$equal_to@PEAU_iobuf@@@3@@std@@V?$allocator@U?$pair@QEAU_iobuf@@PEAX@std@@@3@$0A@@std@@@std@@IEAAX_K@Z()
mysqld.exe!?_Forced_rehash@?$_Hash@V?$_Umap_traits@PEAU_iobuf@@PEAXV?$_Uhash_compare@PEAU_iobuf@@U?$hash@PEAU_iobuf@@@std@@U?$equal_to@PEAU_iobuf@@@3@@std@@V?$allocator@U?$pair@QEAU_iobuf@@PEAX@std@@@3@$0A@@std@@@std@@IEAAX_K@Z()
mysqld.exe!pthread_dummy()
mysqld.exe!pthread_dummy()
mysqld.exe!pthread_dummy()
mysqld.exe!??$_Reallocate_grow_by@V<lambda_1>@?1??append@?$basic_string@DU?$char_traits@D@std@@V?$allocator@D@2@@std@@QEAAAEAV34@QEBD_K@Z@PEBD_K@?$basic_string@DU?$char_traits@D@std@@V?$allocator@D@2@@std@@AEAAAEAV01@_KV<lambda_1>@?1??append@01@QEAAAEAV01@QEBD0@Z@PEBD_K@Z()
mysqld.exe!?ha_initialize_handlerton@@YAHPEAUst_plugin_int@@@Z()
mysqld.exe!?plugin_dl_foreach@@YA_NPEAVTHD@@PEBUst_mysql_const_lex_string@@P6AD0PEAUst_plugin_int@@PEAX@Z3@Z()
mysqld.exe!?plugin_init@@YAHPEAHPEAPEADH@Z()
mysqld.exe!?plugin_init@@YAHPEAHPEAPEADH@Z()
mysqld.exe!?init_net_server_extension@@YAXPEAVTHD@@@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()
The manual page at https://mariadb.com/kb/en/how-to-produce-a-full-stack-trace-for-mariadbd/ 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
2024-03-26 13:36:31 0 [Note] Starting MariaDB 10.4.32-MariaDB source revision c4143f909528e3fab0677a28631d10389354c491 as process 13396
2024-03-26 13:36:31 0 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2024-03-26 13:36:31 0 [Note] InnoDB: Uses event mutexes
2024-03-26 13:36:31 0 [Note] InnoDB: Compressed tables use zlib 1.3
2024-03-26 13:36:31 0 [Note] InnoDB: Number of pools: 1
2024-03-26 13:36:31 0 [Note] InnoDB: Using SSE2 crc32 instructions
2024-03-26 13:36:31 0 [Note] InnoDB: Initializing buffer pool, total size = 16M, instances = 1, chunk size = 16M
2024-03-26 13:36:31 0 [Note] InnoDB: Completed initialization of buffer pool
2024-03-26 13:36:31 0 [Note] InnoDB: Starting crash recovery from checkpoint LSN=41621806
2024-03-26 13:36:31 0 [Note] InnoDB: Starting final batch to recover 5 pages from redo log.
2024-03-26 13:36:31 0 [ERROR] [FATAL] InnoDB: Trying to read page number 49153 in space 0, space name innodb_system, which is outside the tablespace bounds. Byte offset 0, len 16384Please check that the configuration matches the InnoDB system tablespace location (ibdata files)
240326 13:36:31 [ERROR] mysqld got exception 0x80000003 ;
Sorry, 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

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.32-MariaDB source revision: c4143f909528e3fab0677a28631d10389354c491
key_buffer_size=16777216
read_buffer_size=262144
max_used_connections=0
max_threads=65537
thread_count=0
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
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...
mysqld.exe!my_parameter_handler()
ucrtbase.dll!raise()
ucrtbase.dll!abort()
mysqld.exe!??$_Construct@$00PEBD@?$basic_string@DU?$char_traits@D@std@@V?$allocator@D@2@@std@@AEAAXQEBD_K@Z()
mysqld.exe!pthread_dummy()
mysqld.exe!?_Forced_rehash@?$_Hash@V?$_Umap_traits@PEAU_iobuf@@PEAXV?$_Uhash_compare@PEAU_iobuf@@U?$hash@PEAU_iobuf@@@std@@U?$equal_to@PEAU_iobuf@@@3@@std@@V?$allocator@U?$pair@QEAU_iobuf@@PEAX@std@@@3@$0A@@std@@@std@@IEAAX_K@Z()
mysqld.exe!?_Forced_rehash@?$_Hash@V?$_Umap_traits@PEAU_iobuf@@PEAXV?$_Uhash_compare@PEAU_iobuf@@U?$hash@PEAU_iobuf@@@std@@U?$equal_to@PEAU_iobuf@@@3@@std@@V?$allocator@U?$pair@QEAU_iobuf@@PEAX@std@@@3@$0A@@std@@@std@@IEAAX_K@Z()
mysqld.exe!pthread_dummy()
mysqld.exe!pthread_dummy()
mysqld.exe!pthread_dummy()
mysqld.exe!pthread_dummy()
mysqld.exe!pthread_dummy()
mysqld.exe!?_Forced_rehash@?$_Hash@V?$_Umap_traits@PEAU_iobuf@@PEAXV?$_Uhash_compare@PEAU_iobuf@@U?$hash@PEAU_iobuf@@@std@@U?$equal_to@PEAU_iobuf@@@3@@std@@V?$allocator@U?$pair@QEAU_iobuf@@PEAX@std@@@3@$0A@@std@@@std@@IEAAX_K@Z()
mysqld.exe!?_Forced_rehash@?$_Hash@V?$_Umap_traits@PEAU_iobuf@@PEAXV?$_Uhash_compare@PEAU_iobuf@@U?$hash@PEAU_iobuf@@@std@@U?$equal_to@PEAU_iobuf@@@3@@std@@V?$allocator@U?$pair@QEAU_iobuf@@PEAX@std@@@3@$0A@@std@@@std@@IEAAX_K@Z()
mysqld.exe!pthread_dummy()
mysqld.exe!pthread_dummy()
mysqld.exe!pthread_dummy()
mysqld.exe!??$_Reallocate_grow_by@V<lambda_1>@?1??append@?$basic_string@DU?$char_traits@D@std@@V?$allocator@D@2@@std@@QEAAAEAV34@QEBD_K@Z@PEBD_K@?$basic_string@DU?$char_traits@D@std@@V?$allocator@D@2@@std@@AEAAAEAV01@_KV<lambda_1>@?1??append@01@QEAAAEAV01@QEBD0@Z@PEBD_K@Z()
mysqld.exe!?ha_initialize_handlerton@@YAHPEAUst_plugin_int@@@Z()
mysqld.exe!?plugin_dl_foreach@@YA_NPEAVTHD@@PEBUst_mysql_const_lex_string@@P6AD0PEAUst_plugin_int@@PEAX@Z3@Z()
mysqld.exe!?plugin_init@@YAHPEAHPEAPEADH@Z()
mysqld.exe!?plugin_init@@YAHPEAHPEAPEADH@Z()
mysqld.exe!?init_net_server_extension@@YAXPEAVTHD@@@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()
The manual page at https://mariadb.com/kb/en/how-to-produce-a-full-stack-trace-for-mariadbd/ 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