Details
-
Bug
-
Status: Needs Feedback (View Workflow)
-
Major
-
Resolution: Unresolved
-
10.6.19
-
windows
Description
[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.6.19-MariaDB-log source revision: 8f020508c87461bbeee551c3001acac56d506ae7
|
key_buffer_size=134217728
|
read_buffer_size=131072
|
max_used_connections=112
|
max_threads=65537
|
thread_count=111
|
It is possible that mysqld could use up to
|
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 1082300045 K bytes of memory
|
Hope that's ok; if not, decrease some variables in the equation.
|
|
Thread pointer: 0x27d3c35a5e8
|
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...
|
|
server.dll!my_parameter_handler()
|
ucrtbase.dll!raise()
|
ucrtbase.dll!abort()
|
server.dll!json_valid()
|
server.dll!json_valid()
|
server.dll!json_valid()
|
server.dll!json_valid()
|
server.dll!json_valid()
|
server.dll!json_valid()
|
server.dll!json_valid()
|
server.dll!json_valid()
|
ntdll.dll!TpReleaseWork()
|
ntdll.dll!RtlInitializeResource()
|
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
|