Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Incomplete
-
None
-
OS: Windows 10 (64 bits)
CPU: Intel Core I5-7200 2.5Ghz
RAM: 8gb
DISK: 1Tb - Samsung SSD 860 Evo
PRODUCT: MariaDB (MySQL) Version 10.3.13
Description
The engine crash in middle of an insert. There are a lot (20 by sec) of similar inserts to the same table before the crash, the offending insert is not special.
This is the crash:
??
InnoDB: Submit a detailed bug report to https://jira.mariadb.org/ |
2020-08-05 17:06:26 0x1eb8 InnoDB: Assertion failure in file d:\winx64-packages\build\src\storage\innobase\rem\rem0rec.cc line 814 |
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.
|
200805 17:06:26 [ERROR] mysqld got exception 0x80000003 ; |
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.3.13-MariaDB |
key_buffer_size=134217728 |
read_buffer_size=131072 |
max_used_connections=4 |
max_threads=65537 |
thread_count=9 |
It is possible that mysqld could use up to
|
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 136185 K bytes of memory |
Hope that's ok; if not, decrease some variables in the equation. |
|
Thread pointer: 0x1f8e23b5a38 |
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_sigabrt_handler()[my_thr_init.c:485] |
mysqld.exe!raise()[signal.cpp:516] |
mysqld.exe!abort()[abort.cpp:71] |
mysqld.exe!ut_dbg_assertion_failed()[ut0dbg.cc:60] |
mysqld.exe!rec_get_offsets_func()[rem0rec.cc:814] |
mysqld.exe!page_cur_search_with_match()[page0cur.cc:432] |
mysqld.exe!btr_root_raise_and_insert()[btr0btr.cc:2159] |
mysqld.exe!btr_cur_pessimistic_insert()[btr0cur.cc:3629] |
mysqld.exe!btr_insert_on_non_leaf_level_func()[btr0btr.cc:2561] |
mysqld.exe!btr_attach_half_pages()[btr0btr.cc:2682] |
mysqld.exe!btr_page_split_and_insert()[btr0btr.cc:3102] |
mysqld.exe!btr_cur_pessimistic_insert()[btr0cur.cc:3634] |
mysqld.exe!row_ins_clust_index_entry_low()[row0ins.cc:2800] |
mysqld.exe!row_ins_clust_index_entry()[row0ins.cc:3300] |
mysqld.exe!row_ins_index_entry()[row0ins.cc:3410] |
mysqld.exe!row_ins_index_entry_step()[row0ins.cc:3562] |
mysqld.exe!row_ins()[row0ins.cc:3699] |
mysqld.exe!row_ins_step()[row0ins.cc:3947] |
mysqld.exe!row_insert_for_mysql()[row0mysql.cc:1463] |
mysqld.exe!ha_innobase::write_row()[ha_innodb.cc:8061] |
mysqld.exe!handler::ha_write_row()[handler.cc:6285] |
mysqld.exe!write_record()[sql_insert.cc:2020] |
mysqld.exe!mysql_insert()[sql_insert.cc:1063] |
mysqld.exe!mysql_execute_command()[sql_parse.cc:4728] |
mysqld.exe!mysql_parse()[sql_parse.cc:8100] |
mysqld.exe!dispatch_command()[sql_parse.cc:1856] |
mysqld.exe!do_command()[sql_parse.cc:1395] |
mysqld.exe!threadpool_process_request()[threadpool_common.cc:358] |
mysqld.exe!tp_callback()[threadpool_common.cc:186] |
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 (0x1f8e21e7f10): insert into datoenergia (fechahora, dato, idmedidor, idunidad, acumulado) values ('2020-08-05 17:06:24.249042', 30.680145000000003, 9, 7, 212203.469) |
Connection ID (thread ID): 8 |
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=off,table_elimination=on,extended_keys=on,exists_to_in=on,orderby_uses_equalities=on,condition_pushdown_for_derived=on,split_materialized=on |
|
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.
|
|
|
|
??
Attachments
Issue Links
- relates to
-
MDEV-22736 Assertion failure in file rem0rec.cc line 814
-
- Closed
-
This assertion location does look the same as
MDEV-22736however there's nothing else linking these two.10.3.13 is quite an old release now. Are you willing to try on 10.3.24 to see if this bug still occurs?
If it does reoccur can you include you my.ini settings and the table information for datoenergia.
show create table datoenergia