MySQL Bugs: #93545: MYSQL crashing more frequently. Once or twice a week or some time smore

Bug #93545	MYSQL crashing more frequently. Once or twice a week or some time smore
Submitted:	10 Dec 2018 15:46	Modified:	10 Dec 2018 17:08
Reporter:	PAVAN BHANDARI	Email Updates:
Status:	Can't repeat	Impact on me:	None
Category:	MySQL Server	Severity:	S2 (Serious)
Version:		OS:	Windows
Assigned to:		CPU Architecture:	x86

Description:
MYSQL has been crashing frequently. I have been using MYSQL for about 3 years now, and never had issue but it started recently since 2 months.  Following below are the errors in the error log. 

1. unable to allocate memory of size 1065016
2.cant create thread to handle request, assertion failure in thread 26772 in file sync0arr.ic line 60.

Not sure why we are having this issue all of a sudden.

How to repeat:
not sure

Not enough information was provided for us to be able to handle this bug. Please re-read the instructions at http://bugs.mysql.com/how-to-report.php

If you can provide more information, feel free to add it to this bug.

Thank you for your interest in MySQL.

We have been using mysql for about 3 years now and never had this issue before. Issue is MYSQL crashed and stops working all of a sudden by itself until I stop and start it again. Once I stop and start it works. I looked the server error logs and got the following message this morning.

1. Timestamp, Thread, Type, Details
2018-12-10 01:13:38, 19228, ERROR, InnoDB:  InnoDB: Unable to allocate memory of size 1065016.
, , , 2018-12-10 01:13:38 507c  InnoDB: Assertion failure in thread 20604 in file ha_innodb.cc line 17303
, , , 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.

Whevever crash happens I see above message. 

Some times I see the following below message
Timestamp, Thread, Type, Details
2018-12-10 01:13:38, 19228, ERROR, InnoDB:  InnoDB: Unable to allocate memory of size 1065016.
, , , 2018-12-10 01:13:38 507c  InnoDB: Assertion failure in thread 20604 in file ha_innodb.cc line 17303
, , , 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.