Bug #93764 mysql workbench procedure editor has memory leak

• Submitted: 29 Dec 2018 9:03
• Modified: 29 Dec 2018 19:22
• Reporter: rain zhong
• Status: Can't repeat
• Category: MySQL Workbench
• Severity: S1 (Critical)
• Version: 6.3.9
• OS: Windows (Microsoft Windows 10 Pro)
• CPU Architecture: x86
• Tags: WBBugReporter

[29 Dec 2018 9:03] rain zhong

Description:
----[For better reports, please attach the log file after submitting. You can find it in C:\Users\Administrator\AppData\Roaming\MySQL\Workbench\log\wb.log]
i don't operate the workbench for some time so it lose the connect, then i close and reopen it. then i open one procedure and edit. i only type four words then my computer go die. there is no reflection no matter i click any one of the keyboards. after about five minutes it open the task manager. Mysqlworkbench use about 2G memory. then my computer show me the memory is not enough and i foce to close the workbench client.Most of time the workbench only use 100M memory.only if i edit the procedure the memory use increse rapidly. This situlation has occured 3 times so i lose all i type into the editor.

The log is following: there is no any log about ten minutes. Between these times i can do nothing expect close the client and reopen. Hope this can help you find the bug.

How to repeat:
I just type workds in the procedure editor. 3 times it all occured when i edit the procesure.

[29 Dec 2018 9:04] rain zhong

wb file before the memory leak

Attachment: wb.1.log (application/octet-stream, text), 50.74 KiB.

[29 Dec 2018 9:05] rain zhong

log file after the memory leak

Attachment: wb.log (application/octet-stream, text), 51.42 KiB.

[29 Dec 2018 19:22] MySQL Verification Team

Thank you for the bug report. I couldn't repeat with current version 8.0.13.