MySQL Bugs: #92033: Assertion failure

Bug #92033	Assertion failure
Submitted:	16 Aug 2018 1:22	Modified:	16 Aug 2018 4:57
Reporter:	Arthur Daley	Email Updates:
Status:	Duplicate	Impact on me:	None
Category:	MySQL Server: InnoDB storage engine	Severity:	S1 (Critical)
Version:	8.0.12	OS:	Windows (Windows 7 Ultimate SP1 (64-bit))
Assigned to:		CPU Architecture:	Other (64-bit)
Tags:	mysql crash assertion failure

Description:
This problem appears that it may be a bug.

I recently installed mysql. Ever since, the server continually and randomly (it seems) crashes and disconnects from the mysql command-line client, every few minutes, or hours.

The server's error log entry shows 'assertion failure', on each occasion:

[ERROR] [MY-000000] [InnoDB] InnoDB: Assertion failure: log0write.cc:1799:time_elapsed >= 0

The problem occurs with various databases and various SQL commands being executed at the time. I have not been able to determine any particular usage pattern that causes or recreates the crashes.

I have utilised newly created databases/tables, yet, the problem persists.

The problem also occurs, when using Apache/PHP to access the server.

How to repeat:
Access server via mysql command line client. Try various SQL commands. Eventually, server should crash with "assertion failure".

After a crash, I have tried the same SQL command again, to try to repeat the crash. But it doesn't happen, when trying to replicate it (Sods Law). On the surface, it looks like a random crash. But I am sure it just requires a particular combination of events. But I am speculating.

I have uploaded server error log file:
mysql-bug-data-92033_server_error_log.err

Hello Arthur Daley,

Thank you for the report.
This is a duplicate of Bug #90670, which is fixed as of the upcoming 8.0.13 release, and here's the changelog entry:

Adjusting the server time to an earlier time caused periodic redo flushed
to be missed.

Thanks,
Umesh