MariaDB crashed on INSERT (item.cc:6620)

191025 13:17:07 [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.4.8-MariaDB

key_buffer_size=134217728

read_buffer_size=67108864

max_used_connections=36

max_threads=65537

thread_count=11

It is possible that mysqld could use up to 

key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 266289 K  bytes of memory

Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x26cea8e048

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!save_int_value_in_field()[item.cc:6620]

mysqld.exe!fill_record()[sql_base.cc:8491]

mysqld.exe!fill_record_n_invoke_before_triggers()[sql_base.cc:8663]

mysqld.exe!mysql_insert()[sql_insert.cc:961]

mysqld.exe!mysql_execute_command()[sql_parse.cc:4529]

mysqld.exe!mysql_parse()[sql_parse.cc:7914]

mysqld.exe!dispatch_command()[sql_parse.cc:1845]

mysqld.exe!do_command()[sql_parse.cc:1359]

mysqld.exe!threadpool_process_request()[threadpool_common.cc:366]

mysqld.exe!tp_callback()[threadpool_common.cc:193]

KERNEL32.DLL!VirtualUnlock()

ntdll.dll!RtlGetActiveActivationContext()

ntdll.dll!RtlFreeUnicodeString()

KERNEL32.DLL!BaseThreadInitThunk()

ntdll.dll!RtlUserThreadStart()

Trying to get some variables.

Some pointers may be invalid and cause the dump to abort.

Query (0x26b64b1360): insert into Performance (flightRecordId, cashunitErrors, errors, jams, limitedService, logicalExceptions, movedNotes, movedVoucher, nonTechLimitedService, oosErrors, oosJamsHead, oosJamsSafe, unrecoveredErrors, useCase, useCases) values (2834658, 0, 4, 0, 0, 0, 1847, 0, 0, 0, 0, 0, 0, 'ALL', 134)

Connection ID (thread ID): 5572018

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

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 D:\MariaDB 10.4\data\

2019-10-25 13:45:38 46150 [ERROR] InnoDB: Unable to decompress .\fcc_1290\inventorydata.ibd[page id: space=2586, page number=108374]

2019-10-25 13:45:38 46150 [Warning] InnoDB:  Error code: 107 btr_pcur_open_low  level: 0 called from file: D:\winx64-packages\build\src\storage\innobase\row\row0row.cc line: 1225 table: `fcc_1290`.`inventorydata` index: `PRIMARY`

2019-10-25 13:45:38 3 [ERROR] InnoDB: Unable to decompress .\fcc_1290\cashflowstack.ibd[page id: space=2583, page number=323198]

191025 13:45:38 [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.4.8-MariaDB

key_buffer_size=134217728

read_buffer_size=67108864

max_used_connections=43

max_threads=65537

thread_count=22

It is possible that mysqld could use up to 

key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 266289 K  bytes of memory

Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0xdfbc466988

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

2019-10-25 13:45:38 46147 [ERROR] InnoDB: Unable to decompress .\fcc_1290\histogramentry.ibd[page id: space=2585, page number=24568]

2019-10-25 13:45:38 46147 [Warning] InnoDB:  Error code: 107 btr_pcur_open_low  level: 0 called from file: D:\winx64-packages\build\src\storage\innobase\row\row0row.cc line: 1225 table: `fcc_1290`.`histogramentry` index: `PRIMARY`

InnoDB: using atomic writes.