MySQL Bugs: #90651: Out of Memory and Crash

Bug #90651	Out of Memory and Crash
Submitted:	26 Apr 2018 16:42	Modified:	30 Apr 2018 22:45
Reporter:	Tom Renish	Email Updates:
Status:	Can't repeat	Impact on me:	None
Category:	MySQL for Windows: MySQL for Excel	Severity:	S2 (Serious)
Version:	1.3.7	OS:	Windows (Windows 7 Enterprise - 64 bit)
Assigned to:		CPU Architecture:	x86 (Intel Core i7-6600U, 2.6GHz)

Description:
https://forums.mysql.com/read.php?172,665937,665937#msg-665937

Excel will crash completely following an error message stating, "Out of Memory" when using the MySQL for Excel plugin

How to repeat:
Configuration notes:

1) Windows 7 Enterprise 
2) Microsoft Office Professional Plus 2016 - 64 bit 
3) The presence of an auto-loaded workbook in the Excel startup folder. In my case: C:\Users\MyUserName\AppData\Roaming\Microsoft\Excel\XLStart 
4) Most importantly, the file must be *hidden*. 

This hidden workbook's purpose is to hold macros that are accessible to all other workbooks subsequently created or opened

With all the conditions set above, the MySQL for Excel plugin will run continuously without problems. Once the workbook in which the plugin was running is closed, Excel will announce that it is out of memory. A subsequent startup of Excel may also result in an immediate crash. It doesn't seem to matter if the hidden workbook is file type .xlsm or .xlsb 

It occurs to me that this may happen any time a workbook is hidden, but I didn't test for this.

Let me know if you have any questions.

updated OS, CPU info

Step 4 in the introduction is poorly worded.  The file doesn't need to be hidden... the workbook must be hidden via Excel's "hide workbook" function and already saved in that state.

Hello Tom Renish,

Thank you for the bug report.
I tried to reproduce the issue at my end using MS Excel 2016,  MySQL for Excel 1.3.7 but not seeing any issues.
Could you please provide us exact steps ( screenshots, etc. - please make it as private if you prefer) to confirm this issue at our end?

Thanks,
Chiranjeevi.

Well I'm at something of a loss.  Last Friday I couldn't avoid the crashing behavior, but today I can't replicate it.

If there's something I did that corrected the behavior, I don't know what it could be.

Thank you for the feedback. Please comment here when you are able to provide a repeatable test case. Thanks.