MySQL Bugs: #90033: Application memory explosion

Bug #90033	Application memory explosion
Submitted:	12 Mar 2018 20:58	Modified:	13 Apr 2018 8:32
Reporter:	Stephen Herr	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL Workbench	Severity:	S3 (Non-critical)
Version:	6.3.10	OS:	MacOS (macOS 10.12.x Sierra x86_64)
Assigned to:		CPU Architecture:	x86
Tags:	WBBugReporter

Description:
----[For better reports, please attach the log file after submitting. You can find it in /Users/sherr1/Library/Application Support/MySQL/Workbench/log/wb.log]

Was manipulating two stored procedures. Renaming original one for a backup and then renaming a development one to replace the original one. I was then trying to close the various tabs I had open for these stored procedures.

Workbench changed the cursor to the "waiting" spinning colored disk. After a minute or so, the OS reported that all open applications were out of Application Memory Space and paused.

Opened Activity Monitor, not knowing if it would actually work. It did successfully launch. Using the Memory Tab and sorting the list by memory utilization, Workbench was reporting 55.6GB of memory used. I hit 'force quit' on the dialog that had popped up regarding out of application memory space and the process disappeared from the process list and the memory pressure graph at the bottom of the screen dropped dramatically and went green.

My system only has 16GB physical memory and there appears to only be 21GB of SSD disk space left. I have no clue where or how the 55.6GB was allocated to the process.

I can only imagine this could be a possible security issue if the OS had not been able to keep the memory growth allocated to the Application Memory.

How to repeat:
I am not sure what I did that led to the situation except as described above. There were no huge SELECT queries being run at the time. It seemed to be all around closing stored procedure tabs created by the "right-click, Alter Stored Procedure..." functionality. I did have two tabs with the same name, but I have no clue if that was part of the problem.

Thank you for the bug report. We need a repeatable test case with the description is not enough to repeat on our side, if needed provide the stored procedures. Thanks.

No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".