signal 6 with wrong page size during btr_page_reorganize

2019-07-05 11:07:39 0 [Note] /usr/sbin/mysqld: ready for connections.

Version: '10.4.6-MariaDB-log'  socket: '/var/lib/mysql/mysql.sock'  port: 3306  MariaDB Server

2019-07-05 11:07:39 22 [ERROR] InnoDB: Page old data size 10975 new data size 10991, page old max ins size 5255 new max ins size 5239

2019-07-05 11:07:39 22 [ERROR] InnoDB: Submit a detailed bug report to https://jira.mariadb.org/

2019-07-05 11:07:39 0x7f44ec0d9700  InnoDB: Assertion failure in file /home/buildbot/buildbot/padding_for_CPACK_RPM_BUILD_SOURCE_DIRS_PREFIX/mariadb-10.4.6/storage/innobase/btr/btr0cur.cc line 4685

InnoDB: Failing assertion: rec

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.

190705 11:07:39 [ERROR] mysqld got signal 6 ;

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.6-MariaDB-log

key_buffer_size=33554432

read_buffer_size=131072

max_used_connections=3

max_threads=502

thread_count=9

It is possible that mysqld could use up to

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

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

Thread pointer: 0x7f414c0009a8

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

stack_bottom = 0x7f44ec0d8cf0 thread_stack 0x49000

/usr/sbin/mysqld(my_print_stacktrace+0x2e)[0x55909a433d7e]

/usr/sbin/mysqld(handle_fatal_signal+0x30f)[0x559099ec67af]

sigaction.c:0(__restore_rt)[0x7f44f26ac5d0]

:0(__GI_raise)[0x7f44f097f207]

:0(__GI_abort)[0x7f44f09808f8]

/usr/sbin/mysqld(+0x59948a)[0x559099bc648a]

/usr/sbin/mysqld(+0xbab868)[0x55909a1d8868]

/usr/sbin/mysqld(+0xb325c3)[0x55909a15f5c3]

/usr/sbin/mysqld(+0xb376c9)[0x55909a1646c9]

/usr/sbin/mysqld(+0xb382b4)[0x55909a1652b4]

/usr/sbin/mysqld(+0xb0f34b)[0x55909a13c34b]

/usr/sbin/mysqld(+0xa46532)[0x55909a073532]

/usr/sbin/mysqld(_ZN7handler13ha_update_rowEPKhS1_+0x377)[0x559099ed2937]

/usr/sbin/mysqld(_Z12write_recordP3THDP5TABLEP12st_copy_info+0x7df)[0x559099c8a9cf]

/usr/sbin/mysqld(_Z12mysql_insertP3THDP10TABLE_LISTR4ListI4ItemERS3_IS5_ES6_S6_15enum_duplicatesb+0x1100)[0x559099c90b70]

/usr/sbin/mysqld(_Z21mysql_execute_commandP3THD+0x3f32)[0x559099cbfad2]

/usr/sbin/mysqld(_Z11mysql_parseP3THDPcjP12Parser_statebb+0x24b)[0x559099cc514b]

/usr/sbin/mysqld(_Z16dispatch_command19enum_server_commandP3THDPcjbb+0x1b66)[0x559099cc7ed6]

/usr/sbin/mysqld(_Z10do_commandP3THD+0x11c)[0x559099cc94ac]

/usr/sbin/mysqld(_Z24do_handle_one_connectionP7CONNECT+0x21a)[0x559099da4d6a]

/usr/sbin/mysqld(handle_one_connection+0x3d)[0x559099da4ecd]

pthread_create.c:0(start_thread)[0x7f44f26a4dd5]

/lib64/libc.so.6(clone+0x6d)[0x7f44f0a46ead]

Trying to get some variables.

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

Query (0x7f414c00fd70): insert into  [....]

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

Working directory at /var/lib/mysql

Resource Limits:

Limit                     Soft Limit           Hard Limit           Units

Max cpu time              unlimited            unlimited            seconds

Max file size             unlimited            unlimited            bytes

Max data size             unlimited            unlimited            bytes

Max stack size            8388608              unlimited            bytes

Max core file size        0                    unlimited            bytes

Max resident set          unlimited            unlimited            bytes

Max processes             256935               256935               processes

Max open files            16364                16364                files

Max locked memory         65536                65536                bytes

Max address space         unlimited            unlimited            bytes

Max file locks            unlimited            unlimited            locks

Max pending signals       256935               256935               signals

Max msgqueue size         819200               819200               bytes

Max nice priority         0                    0

Max realtime priority     0                    0

Max realtime timeout      unlimited            unlimited            us

Core pattern: core