InnoDB: using atomic writes.
2023-10-08  9:45:34 0 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2023-10-08  9:45:34 0 [Note] InnoDB: Uses event mutexes
2023-10-08  9:45:34 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
2023-10-08  9:45:34 0 [Note] InnoDB: Number of pools: 1
2023-10-08  9:45:34 0 [Note] InnoDB: Using SSE2 crc32 instructions
2023-10-08  9:45:34 0 [Note] InnoDB: Initializing buffer pool, total size = 512M, instances = 1, chunk size = 128M
2023-10-08  9:45:35 0 [Note] InnoDB: Completed initialization of buffer pool
2023-10-08  9:45:35 0 [Note] InnoDB: Starting crash recovery from checkpoint LSN=1661054190
2023-10-08  9:45:35 0 [Note] InnoDB: 1 transaction(s) which must be rolled back or cleaned up in total 0 row operations to undo
2023-10-08  9:45:35 0 [Note] InnoDB: Trx id counter is 2526358
2023-10-08  9:45:35 0 [Note] InnoDB: Starting final batch to recover 24 pages from redo log.
2023-10-08  9:45:35 0 [Note] InnoDB: 128 out of 128 rollback segments are active.
2023-10-08  9:45:35 0 [Note] InnoDB: Starting in background the rollback of recovered transactions
2023-10-08 09:45:35 0x213c  InnoDB: Assertion failure in file D:\winx64-packages\build\src\storage\innobase\include\fut0lst.ic line 67
InnoDB: Failing assertion: addr.page == FIL_NULL || addr.boffset >= FIL_PAGE_DATA
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.
2023-10-08  9:45:35 0 [Note] InnoDB: Re231008  9:45:35 m[ERROR] mysqld got exception 0x80000003 ;
oThis 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.

vTo report this bug, see https://mariadb.com/kb/en/reporting-bugs

eWe 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.

dServer version: 10.4.14-MariaDB
 key_buffer_size=16777216
tread_buffer_size=2097152
emax_used_connections=0
mmax_threads=65537
pthread_count=0
oIt is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 32885 K  bytes of memory
rHope that's ok; if not, decrease some variables in the equation.

aThread pointer: 0x0
rAttempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
y tablespace data file: "ibtmp1"
2023-10-08  9:45:35 0 [Note] InnoDB: Creating shared tablespace for temporary tables
2023-10-08  9:45:35 0 [Note] InnoDB: Setting file '.\ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2023-10-08  9:45:35 0 [Note] InnoDB: File '.\ibtmp1' size is now 12 MB.
2023-10-08  9:45:35 0 [Note] InnoDB: Waiting for purge to start
mysqld.exe!my_parameter_handler()
ucrtbase.dll!raise()
ucrtbase.dll!abort()
mysqld.exe!?append@?$basic_string@DU?$char_traits@D@std@@V?$allocator@D@2@@std@@QEAAAEAV12@QEBD_K@Z()
mysqld.exe!??$?0V?$tuple@AEBQEAU_iobuf@@@std@@V?$tuple@$$V@1@$0A@$$Z$S@?$pair@QEAU_iobuf@@PEAX@std@@QEAA@AEAV?$tuple@AEBQEAU_iobuf@@@1@AEAV?$tuple@$$V@1@U?$integer_sequence@_K$0A@@1@U?$integer_sequence@_K$S@1@@Z()
mysqld.exe!??$?0V?$tuple@AEBQEAU_iobuf@@@std@@V?$tuple@$$V@1@$0A@$$Z$S@?$pair@QEAU_iobuf@@PEAX@std@@QEAA@AEAV?$tuple@AEBQEAU_iobuf@@@1@AEAV?$tuple@$$V@1@U?$integer_sequence@_K$0A@@1@U?$integer_sequence@_K$S@1@@Z()
mysqld.exe!pthread_dummy()
mysqld.exe!??$?0V?$tuple@AEBQEAU_iobuf@@@std@@V?$tuple@$$V@1@$0A@$$Z$S@?$pair@QEAU_iobuf@@PEAX@std@@QEAA@AEAV?$tuple@AEBQEAU_iobuf@@@1@AEAV?$tuple@$$V@1@U?$integer_sequence@_K$0A@@1@U?$integer_sequence@_K$S@1@@Z()
mysqld.exe!??$?0V?$tuple@AEBQEAU_iobuf@@@std@@V?$tuple@$$V@1@$0A@$$Z$S@?$pair@QEAU_iobuf@@PEAX@std@@QEAA@AEAV?$tuple@AEBQEAU_iobuf@@@1@AEAV?$tuple@$$V@1@U?$integer_sequence@_K$0A@@1@U?$integer_sequence@_K$S@1@@Z()
mysqld.exe!??$?0V?$tuple@AEBQEAU_iobuf@@@std@@V?$tuple@$$V@1@$0A@$$Z$S@?$pair@QEAU_iobuf@@PEAX@std@@QEAA@AEAV?$tuple@AEBQEAU_iobuf@@@1@AEAV?$tuple@$$V@1@U?$integer_sequence@_K$0A@@1@U?$integer_sequence@_K$S@1@@Z()
mysqld.exe!??$?0V?$tuple@AEBQEAU_iobuf@@@std@@V?$tuple@$$V@1@$0A@$$Z$S@?$pair@QEAU_iobuf@@PEAX@std@@QEAA@AEAV?$tuple@AEBQEAU_iobuf@@@1@AEAV?$tuple@$$V@1@U?$integer_sequence@_K$0A@@1@U?$integer_sequence@_K$S@1@@Z()
mysqld.exe!??$?0V?$tuple@AEBQEAU_iobuf@@@std@@V?$tuple@$$V@1@$0A@$$Z$S@?$pair@QEAU_iobuf@@PEAX@std@@QEAA@AEAV?$tuple@AEBQEAU_iobuf@@@1@AEAV?$tuple@$$V@1@U?$integer_sequence@_K$0A@@1@U?$integer_sequence@_K$S@1@@Z()
mysqld.exe!??$?0V?$tuple@AEBQEAU_iobuf@@@std@@V?$tuple@$$V@1@$0A@$$Z$S@?$pair@QEAU_iobuf@@PEAX@std@@QEAA@AEAV?$tuple@AEBQEAU_iobuf@@@1@AEAV?$tuple@$$V@1@U?$integer_sequence@_K$0A@@1@U?$integer_sequence@_K$S@1@@Z()
mysqld.exe!??$?0V?$tuple@AEBQEAU_iobuf@@@std@@V?$tuple@$$V@1@$0A@$$Z$S@?$pair@QEAU_iobuf@@PEAX@std@@QEAA@AEAV?$tuple@AEBQEAU_iobuf@@@1@AEAV?$tuple@$$V@1@U?$integer_sequence@_K$0A@@1@U?$integer_sequence@_K$S@1@@Z()
KERNEL32.DLL!BaseThreadInitThunk()
ntdll.dll!RtlUserThreadStart()
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:\zentao\ZenTao\bin\mysql\data\
2023-10-08  9:45:36 0 [Note] InnoDB: 10.4.14 started; log sequence numbeMinidump written to C:\zentao\ZenTao\bin\mysql\data\mysqld.dmp
r 1661086282; transaction id 2526361
2023-10-08  9:45:36 0 [Note] Plugin 'FEEDBACK' is disabled.
2023-10-08  9:45:36 0 [Note] InnoDB: Loading buffer pool(s) from C:\zentao\ZenTao\bin\mysql\data\ib_buffer_pool
2023-10-08  9:45:36 0 [Note] Server socket created on IP: '127.0.0.1'.
2023-10-08  9:45:36 0 [Note] Reading of all Master_info entries succeeded
2023-10-08  9:45:36 0 [Note] Added new Master_info '' to hash table
2023-10-08  9:45:36 0 [Note] C:\zentao\ZenTao\bin\mysql\bin\mysqld.exe: ready for connections.
Version: '10.4.14-MariaDB'  socket: ''  port: 3306  mariadb.org binary distribution
InnoDB: using atomic writes.
2023-10-08  9:45:54 0 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2023-10-08  9:45:54 0 [Note] InnoDB: Uses event mutexes
2023-10-08  9:45:54 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
2023-10-08  9:45:54 0 [Note] InnoDB: Number of pools: 1
2023-10-08  9:45:54 0 [Note] InnoDB: Using SSE2 crc32 instructions
2023-10-08  9:45:54 0 [Note] InnoDB: Initializing buffer pool, total size = 512M, instances = 1, chunk size = 128M
2023-10-08  9:45:55 0 [Note] InnoDB: Completed initialization of buffer pool
2023-10-08  9:45:55 0 [Note] InnoDB: Starting crash recovery from checkpoint LSN=1661054190
2023-10-08  9:45:55 0 [Note] InnoDB: 1 transaction(s) which must be rolled back or cleaned up in total 0 row operations to undo
2023-10-08  9:45:55 0 [Note] InnoDB: Trx id counter is 2526367
2023-10-08  9:45:55 0 [Note] InnoDB: Starting final batch to recover 24 pages from redo log.
2023-10-08  9:45:56 0 [Note] InnoDB: 128 out of 128 rollback segments are active.
2023-10-08  9:45:56 0 [Note] InnoDB: Starting in background the rollback of recovered transactions
2023-10-08 09:45:56 0x2750  InnoDB: Assertion failure in file D:\winx64-packages\build\src\storage\innobase\include\fut0lst.ic line 67
InnoDB: Failing assertion: addr.page == FIL_NULL || addr.boffset >= FIL_PAGE_DATA
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.
2023-10-08  9:45:56 0 [Note] InnoDB: Remov231008  9:45:56 e[ERROR] mysqld got exception 0x80000003 ;
dThis 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

tWe 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.

eServer version: 10.4.14-MariaDB
mkey_buffer_size=16777216
pread_buffer_size=2097152
omax_used_connections=0
rmax_threads=65537
athread_count=0
rIt is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 32885 K  bytes of memory
yHope that's ok; if not, decrease some variables in the equation.

 Thread pointer: 0x0
tAttempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
ablespace data file: "ibtmp1"
2023-10-08  9:45:56 0 [Note] InnoDB: Creating shared tablespace for temporary tables
2023-10-08  9:45:56 0 [Note] InnoDB: Setting file '.\ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2023-10-08  9:45:56 0 [Note] InnoDB: File '.\ibtmp1' size is now 12 MB.
2023-10-08  9:45:56 0 [Note] InnoDB: Waiting for purge to start
mysqld.exe!my_parameter_handler()
ucrtbase.dll!raise()
ucrtbase.dll!abort()
mysqld.exe!?append@?$basic_string@DU?$char_traits@D@std@@V?$allocator@D@2@@std@@QEAAAEAV12@QEBD_K@Z()
mysqld.exe!??$?0V?$tuple@AEBQEAU_iobuf@@@std@@V?$tuple@$$V@1@$0A@$$Z$S@?$pair@QEAU_iobuf@@PEAX@std@@QEAA@AEAV?$tuple@AEBQEAU_iobuf@@@1@AEAV?$tuple@$$V@1@U?$integer_sequence@_K$0A@@1@U?$integer_sequence@_K$S@1@@Z()
mysqld.exe!??$?0V?$tuple@AEBQEAU_iobuf@@@std@@V?$tuple@$$V@1@$0A@$$Z$S@?$pair@QEAU_iobuf@@PEAX@std@@QEAA@AEAV?$tuple@AEBQEAU_iobuf@@@1@AEAV?$tuple@$$V@1@U?$integer_sequence@_K$0A@@1@U?$integer_sequence@_K$S@1@@Z()
mysqld.exe!pthread_dummy()
mysqld.exe!??$?0V?$tuple@AEBQEAU_iobuf@@@std@@V?$tuple@$$V@1@$0A@$$Z$S@?$pair@QEAU_iobuf@@PEAX@std@@QEAA@AEAV?$tuple@AEBQEAU_iobuf@@@1@AEAV?$tuple@$$V@1@U?$integer_sequence@_K$0A@@1@U?$integer_sequence@_K$S@1@@Z()
mysqld.exe!??$?0V?$tuple@AEBQEAU_iobuf@@@std@@V?$tuple@$$V@1@$0A@$$Z$S@?$pair@QEAU_iobuf@@PEAX@std@@QEAA@AEAV?$tuple@AEBQEAU_iobuf@@@1@AEAV?$tuple@$$V@1@U?$integer_sequence@_K$0A@@1@U?$integer_sequence@_K$S@1@@Z()
mysqld.exe!??$?0V?$tuple@AEBQEAU_iobuf@@@std@@V?$tuple@$$V@1@$0A@$$Z$S@?$pair@QEAU_iobuf@@PEAX@std@@QEAA@AEAV?$tuple@AEBQEAU_iobuf@@@1@AEAV?$tuple@$$V@1@U?$integer_sequence@_K$0A@@1@U?$integer_sequence@_K$S@1@@Z()
mysqld.exe!??$?0V?$tuple@AEBQEAU_iobuf@@@std@@V?$tuple@$$V@1@$0A@$$Z$S@?$pair@QEAU_iobuf@@PEAX@std@@QEAA@AEAV?$tuple@AEBQEAU_iobuf@@@1@AEAV?$tuple@$$V@1@U?$integer_sequence@_K$0A@@1@U?$integer_sequence@_K$S@1@@Z()
mysqld.exe!??$?0V?$tuple@AEBQEAU_iobuf@@@std@@V?$tuple@$$V@1@$0A@$$Z$S@?$pair@QEAU_iobuf@@PEAX@std@@QEAA@AEAV?$tuple@AEBQEAU_iobuf@@@1@AEAV?$tuple@$$V@1@U?$integer_sequence@_K$0A@@1@U?$integer_sequence@_K$S@1@@Z()
mysqld.exe!??$?0V?$tuple@AEBQEAU_iobuf@@@std@@V?$tuple@$$V@1@$0A@$$Z$S@?$pair@QEAU_iobuf@@PEAX@std@@QEAA@AEAV?$tuple@AEBQEAU_iobuf@@@1@AEAV?$tuple@$$V@1@U?$integer_sequence@_K$0A@@1@U?$integer_sequence@_K$S@1@@Z()
mysqld.exe!??$?0V?$tuple@AEBQEAU_iobuf@@@std@@V?$tuple@$$V@1@$0A@$$Z$S@?$pair@QEAU_iobuf@@PEAX@std@@QEAA@AEAV?$tuple@AEBQEAU_iobuf@@@1@AEAV?$tuple@$$V@1@U?$integer_sequence@_K$0A@@1@U?$integer_sequence@_K$S@1@@Z()
KERNEL32.DLL!BaseThreadInitThunk()
ntdll.dll!RtlUserThreadStart()
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:\zentao\ZenTao\bin\mysql\data\
2023-10-08  9:45:56 0 [Note] InnoDB: 10.4.14 started; log sequence number 1661087289; transaction id 2526370
Minidump written to C:\zentao\ZenTao\bin\mysql\data\mysqld.dmp
2023-10-08  9:45:56 0 [Note] Plugin 'FEEDBACK' is disabled.
2023-10-08  9:45:56 0 [Note] InnoDB: Loading buffer pool(s) from C:\zentao\ZenTao\bin\mysql\data\ib_buffer_pool
2023-10-08  9:45:56 0 [Note] Server socket created on IP: '127.0.0.1'.
2023-10-08  9:45:56 0 [Note] Reading of all Master_info entries succeeded
2023-10-08  9:45:56 0 [Note] Added new Master_info '' to hash table
2023-10-08  9:45:56 0 [Note] C:\zentao\ZenTao\bin\mysql\bin\mysqld.exe: ready for connections.
Version: '10.4.14-MariaDB'  socket: ''  port: 3306  mariadb.org binary distribution