Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Incomplete
-
10.5.2
-
Windows 10 Pro
Description
Hi
Just installed the latest version of Maria DB on a re-installed Windows PC. Normally don't have any issues, but I have SP generator in C# that creates the CRUD Stored Procedures from Tables.
When I run this on 4 simple tables (very simple) it has a fatal error everytime on one simple table.
I have dropped and re-created the table, but I still get the issue.
Log file below
InnoDB: using atomic writes.
|
2020-04-16 15:56:41 0 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
|
2020-04-16 15:56:41 0 [Note] InnoDB: Uses event mutexes
|
2020-04-16 15:56:41 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
|
2020-04-16 15:56:41 0 [Note] InnoDB: Number of pools: 1
|
2020-04-16 15:56:41 0 [Note] InnoDB: Using SSE2 crc32 instructions
|
2020-04-16 15:56:41 0 [Note] InnoDB: Initializing buffer pool, total size = 2147483648, chunk size = 134217728
|
2020-04-16 15:56:41 0 [Note] InnoDB: Completed initialization of buffer pool
|
2020-04-16 15:56:41 0 [Note] InnoDB: 128 rollback segments are active.
|
2020-04-16 15:56:41 0 [Note] InnoDB: Creating shared tablespace for temporary tables
|
2020-04-16 15:56:41 0 [Note] InnoDB: Setting file '.\ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
|
2020-04-16 15:56:41 0 [Note] InnoDB: File '.\ibtmp1' size is now 12 MB.
|
2020-04-16 15:56:41 0 [Note] InnoDB: 10.5.2 started; log sequence number 67923; transaction id 98
|
2020-04-16 15:56:41 0 [Note] Plugin 'FEEDBACK' is disabled.
|
2020-04-16 15:56:41 0 [Note] InnoDB: Loading buffer pool(s) from E:\MariaDB\data\ib_buffer_pool
|
2020-04-16 15:56:42 0 [Note] Server socket created on IP: '::'.
|
2020-04-16 15:56:42 0 [Note] InnoDB: Buffer pool(s) load completed at 200416 15:56:42
|
2020-04-16 15:56:42 0 [Note] Reading of all Master_info entries succeeded
|
2020-04-16 15:56:42 0 [Note] Added new Master_info '' to hash table
|
2020-04-16 15:56:42 0 [Note] E:\MariaDB\bin\mysqld.exe: ready for connections.
|
Version: '10.5.2-MariaDB' socket: '' port: 3306 mariadb.org binary distribution
|
2020-04-16 15:57:38 3 [Warning] Aborted connection 3 to db: 'Tours' user: 'root' host: 'localhost' (Got an error reading communication packets)
|
2020-04-16 15:59:36 4 [Warning] Aborted connection 4 to db: 'Tours' user: 'root' host: 'localhost' (Got an error reading communication packets)
|
200416 16:04:24 [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.5.2-MariaDB
|
key_buffer_size=134217728
|
read_buffer_size=131072
|
max_used_connections=2
|
max_threads=65537
|
thread_count=3
|
It is possible that mysqld could use up to
|
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 136421 K bytes of memory
|
Hope that's ok; if not, decrease some variables in the equation.
|
|
Thread pointer: 0x20770a0dce8
|
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!Binary_string::copy_printable_hhhh()[sql_string.cc:788]
|
mysqld.exe!Protocol::store_warning()[protocol.cc:1199]
|
mysqld.exe!mysqld_show_warnings()[sql_error.cc:827]
|
mysqld.exe!mysql_execute_command()[sql_parse.cc:3971]
|
mysqld.exe!mysql_parse()[sql_parse.cc:7957]
|
mysqld.exe!dispatch_command()[sql_parse.cc:1842]
|
mysqld.exe!do_command()[sql_parse.cc:1358]
|
mysqld.exe!threadpool_process_request()[threadpool_common.cc:357]
|
mysqld.exe!tp_callback()[threadpool_common.cc:196]
|
ntdll.dll!TpReleaseWait()
|
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 (0x2079df500b0): SHOW WARNINGS
|
Connection ID (thread ID): 7
|
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,not_null_range_scan=off
|
|
The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
|
information that should help you find out what is causing the crash.
|
Writing a core file at E:\MariaDB\data\
|
Attachments
Issue Links
- relates to
-
MDEV-22130 SHOW WARNINGS will SIGSEGV 10.5 optimized build after setting CHARACTER_SET_RESULTS to NULL and running any invalid SQL | Binary_string::copy_printable_hhhh
-
- Closed
-
Can
MDEV-22130explain what happens with your generator?If you are not sure, can you enable general log on the server, run the queries leading to the crash and then provide the recorded log?