170404 20:12:54 [ERROR] mysqld.exe: Can't find record in '#sql-1bf0_a'

2017-04-04 17:16:42 f24  InnoDB: Assertion failure in thread 3876 in file dict0stats.cc line 2156

InnoDB: Failing assertion: total_recs > 0

InnoDB: We intentionally generate a memory trap.

InnoDB: Submit a detailed bug report to http://bugs.mysql.com.

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: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html

InnoDB: about forcing recovery.

abort() has been called170404 20:16:42 [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.0.31-MariaDB-debug

key_buffer_size=1048576

read_buffer_size=131072

max_used_connections=7

max_threads=501

thread_count=6

It is possible that mysqld could use up to 

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

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

Thread pointer: 0x0

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:488]

mysqld.exe!raise()[signal.cpp:522]

mysqld.exe!abort()[abort.cpp:71]

mysqld.exe!dict_stats_analyze_index()[dict0stats.cc:2156]

mysqld.exe!dict_stats_update_persistent()[dict0stats.cc:2235]

mysqld.exe!dict_stats_update()[dict0stats.cc:3159]

mysqld.exe!dict_stats_process_entry_from_recalc_pool()[dict0stats_bg.cc:318]

mysqld.exe!dict_stats_thread()[dict0stats_bg.cc:359]

KERNEL32.DLL!BaseThreadInitThunk()

ntdll.dll!RtlUserThreadStart()

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

Minidump written to E:\buildbot\vardirs\10.0-3382\optim-crash-tests\current1_1\master-data\mysqld.dmp

########### End of last lines from the error log for E:\buildbot\vardirs\10.0-3382\optim-crash-tests\trial5.log ###

# 2017-04-04T17:11:51 [4056] Starting: E:\buildbot\rqg/runall.pl --no-mask --seed=time --threads=5 --duration=600 --queries=100M --reporters=QueryTimeout,Backtrace,ErrorLog,Deadlock,Shutdown --redefine=conf/mariadb/redefine_random_keys.yy --redefine=conf/mariadb/redefine_set_session_vars.yy --validators=TransformerNoComparator --transformers=ConvertSubqueriesToViews,DisableOptimizations,EnableOptimizations,ExecuteAsCTE,ExecuteAsInsertSelect,ExecuteAsPreparedOnce,ExecuteAsSelectItem,ExecuteAsUnion,ExecuteAsUpdateDelete,ExecuteAsView,NullIf,OrderBy,StraightJoin,ExecuteAsExecuteImmediate --grammar=conf/mariadb/optimizer_basic.yy --gendata=conf/mariadb/optimizer_basic.zz --mtr-build-thread=300 --basedir1=D:\win-rqg-se\build-debug --vardir1=E:\buildbot\vardirs\10.0-3382\optim-crash-tests/current1_1

Converting --seed=time to --seed=1491325927