Bug #92436 InnoDB: Assertion failure in thread 3312 in file trx0trx.ic line 213
Submitted: 15 Sep 2018 14:16 Modified: 15 Sep 2018 16:18
Reporter: Luis Cavazos Email Updates:
Status: Can't repeat Impact on me:
Category:MySQL Server: DML Severity:S2 (Serious)
Version:5.7.23 OS:Microsoft Windows (Server 2012 )
Assigned to: CPU Architecture:x86 (Intel Xeon cpu e5-2609 2.4ghz ( 2 processors ))
Tags: assertion failure

[15 Sep 2018 14:16] Luis Cavazos
Mysql Crashing very often.

2018-09-15 06:38:24 0xcf0  InnoDB: Assertion failure in thread 3312 in file trx0trx.ic line 213
InnoDB: Failing assertion: !trx->has_search_latch
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.7/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
12:38:25 UTC - 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.
Attempting to collect some information that could help diagnose the problem.
As this is a crash and something is definitely wrong, the information
collection process might fail.

It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 1536687 K  bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x5da8b564f0
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...
7f65ee92222    mysqld.exe!my_sigabrt_handler()[my_thr_init.c:449]
7fff1a6ee1d    MSVCR120.dll!raise()
7fff1a74a14    MSVCR120.dll!abort()
7f65efae0e4    mysqld.exe!ut_dbg_assertion_failed()[ut0dbg.cc:67]
7f65eede593    mysqld.exe!TrxInInnoDB::exit()[trx0trx.h:1517]
7f65eedc9f1    mysqld.exe!ha_innobase::end_stmt()[ha_innodb.cc:15359]
7f65e8140fd    mysqld.exe!close_thread_table()[sql_base.cc:1760]
7f65e813450    mysqld.exe!close_open_tables()[sql_base.cc:1442]
7f65e814470    mysqld.exe!close_thread_tables()[sql_base.cc:1724]
7f65e957f79    mysqld.exe!Prepared_statement::prepare()[sql_prepare.cc:3340]
7f65e9579fe    mysqld.exe!mysqld_stmt_prepare()[sql_prepare.cc:2114]
7f65e774985    mysqld.exe!dispatch_command()[sql_parse.cc:1442]
7f65e775a5a    mysqld.exe!do_command()[sql_parse.cc:1027]
7f65e71c10c    mysqld.exe!handle_connection()[connection_handler_per_thread.cc:300]
7f65f180672    mysqld.exe!pfs_spawn_thread()[pfs.cc:2193]
7f65ee9208c    mysqld.exe!win_thread_start()[my_thread.c:38]
7fff1a24f7f    MSVCR120.dll!_beginthreadex()
7fff1a25126    MSVCR120.dll!_endthreadex()
7f8093a1832    KERNEL32.DLL!BaseThreadInitThunk()
7f80b77e379    ntdll.dll!RtlUserThreadStart()

Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (5dbdd7f7e0): update equipo set equpto =? where idequ =?
Connection ID (thread ID): 92

innodb_buffer_pool_size = 32G

innodb_log_buffer_size = 128M  


event_scheduler = ON

## Tiempo para desconeccion de connexiones inactivas 

# Incremento La Capacidad de IO en Disk

innodb_io_capacity = 1000
innodb_io_capacity_max = 2000
innodb_write_io_threads	= 5
innodb_read_io_threads = 5
innodb_flush_log_at_trx_commit = 2 

join_buffer_size = 256K
sort_buffer_size = 64M
read_rnd_buffer_size = 64M 



How to repeat:
I have not found any, just happens.
[15 Sep 2018 16:18] Miguel Solorzano
Thank you for the bug report. We need a repeatable test case to verify this bug report. Please comment here when you will able to provide it so we will change the status to open and test it. Thanks in advance.