Bug #104320 Random crash when click "Apply" modifying a Store Procedure
Submitted: 14 Jul 2021 19:06 Modified: 20 Jul 2021 15:54
Reporter: Michael Aguilar Email Updates:
Status: Can't repeat Impact on me:
None 
Category:MySQL Workbench Severity:S2 (Serious)
Version:8.0.26 OS:Windows (Windows 10)
Assigned to: CPU Architecture:x86

[14 Jul 2021 19:06] Michael Aguilar 
Description:
The application randomly crash when I click the button "Apply" trying to modifying a Store Procedure.

This happens in 3 different PCs (1 from work, 2 from home)

This appears in the Event Viewers:

Application: MySQLWorkbench.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.AccessViolationException
   at MySQL.Grt.BaseEditorWrapper.apply_changes_to_live_object()
   at System.Windows.Forms.Control.OnClick(System.EventArgs)
   at System.Windows.Forms.Button.OnClick(System.EventArgs)
   at System.Windows.Forms.Button.WndProc(System.Windows.Forms.Message ByRef)
   at System.Windows.Forms.NativeWindow.Callback(IntPtr, Int32, IntPtr, IntPtr)
   at System.Windows.Forms.UnsafeNativeMethods.SendMessage(System.Runtime.InteropServices.HandleRef, Int32, IntPtr, IntPtr)
   at System.Windows.Forms.Control.SendMessage(Int32, IntPtr, IntPtr)
   at System.Windows.Forms.Control.ReflectMessageInternal(IntPtr, System.Windows.Forms.Message ByRef)
   at System.Windows.Forms.Control.WmCommand(System.Windows.Forms.Message ByRef)
   at System.Windows.Forms.Control.WndProc(System.Windows.Forms.Message ByRef)
   at System.Windows.Forms.NativeWindow.Callback(IntPtr, Int32, IntPtr, IntPtr)
   at System.Windows.Forms.UnsafeNativeMethods.CallWindowProc(IntPtr, IntPtr, Int32, IntPtr, IntPtr)
   at System.Windows.Forms.NativeWindow.DefWndProc(System.Windows.Forms.Message ByRef)
   at System.Windows.Forms.Control.WmMouseUp(System.Windows.Forms.Message ByRef, System.Windows.Forms.MouseButtons, Int32)
   at System.Windows.Forms.Control.WndProc(System.Windows.Forms.Message ByRef)
   at System.Windows.Forms.ButtonBase.WndProc(System.Windows.Forms.Message ByRef)
   at System.Windows.Forms.Button.WndProc(System.Windows.Forms.Message ByRef)
   at System.Windows.Forms.NativeWindow.Callback(IntPtr, Int32, IntPtr, IntPtr)
   at System.Windows.Forms.UnsafeNativeMethods.DispatchMessageW(MSG ByRef)
   at System.Windows.Forms.Application+ComponentManager.System.Windows.Forms.UnsafeNativeMethods.IMsoComponentManager.FPushMessageLoop(IntPtr, Int32, Int32)
   at System.Windows.Forms.Application+ThreadContext.RunMessageLoopInner(Int32, System.Windows.Forms.ApplicationContext)
   at System.Windows.Forms.Application+ThreadContext.RunMessageLoop(Int32, System.Windows.Forms.ApplicationContext)
   at MySQL.GUI.Workbench.Program.Main(System.String[])

Faulting application name: MySQLWorkbench.exe, version: 8.0.24.0, time stamp: 0x605f77d8
Faulting module name: db.mysql.parser.grt.dll, version: 0.0.0.0, time stamp: 0x605f777b
Exception code: 0xc0000005
Fault offset: 0x00000000000505c0
Faulting process id: 0x3828
Faulting application start time: 0x01d778abb84e2b67
Faulting application path: C:\Program Files\MySQL\MySQL Workbench 8.0\MySQLWorkbench.exe
Faulting module path: C:\Program Files\MySQL\MySQL Workbench 8.0\db.mysql.parser.grt.dll
Report Id: 3cd4868d-0dd5-4105-8c25-74a2817a9af5
Faulting package full name: 
Faulting package-relative application ID: 

How to repeat:
1. Create a large Store Procedure (More than 500 lines)
2. Right click the new store procedure / Alter Stored Procedured
3. Modify the Store Procedure
4. Apply
[15 Jul 2021 12:08] MySQL Verification Team 
Hello Michael Aguilar,

Thank you for the bug report.
Could you please provide sample stored procedure (please make it as private if you prefer) to confirm this issue at our end?

Regards,
Ashwini Patil
[15 Jul 2021 15:17] Michael Aguilar 
Now happened in other machine, here the event viewer:

Application: MySQLWorkbench.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.AccessViolationException
   at MySQL.Grt.BaseEditorWrapper.apply_changes_to_live_object()
   at System.Windows.Forms.Control.OnClick(System.EventArgs)
   at System.Windows.Forms.Button.OnClick(System.EventArgs)
   at System.Windows.Forms.Button.WndProc(System.Windows.Forms.Message ByRef)
   at System.Windows.Forms.NativeWindow.Callback(IntPtr, Int32, IntPtr, IntPtr)

Faulting application name: MySQLWorkbench.exe, version: 8.0.23.0, time stamp: 0x5fdaedc8
Faulting module name: antlr4-runtime.dll, version: 0.0.0.0, time stamp: 0x5f86f4c4
Exception code: 0xc0000005
Fault offset: 0x0000000000049afc
Faulting process id: 0x26fc
Faulting application start time: 0x01d77902adb2f1f7
Faulting application path: C:\Program Files\MySQL\MySQL Workbench 8.0 CE\MySQLWorkbench.exe
Faulting module path: C:\Program Files\MySQL\MySQL Workbench 8.0 CE\antlr4-runtime.dll
Report Id: 5e88e6a3-4b26-4b33-a78d-ce688893c40a
Faulting package full name: 
Faulting package-relative application ID:
[16 Jul 2021 12:17] MySQL Verification Team 
Hello Michael Aguilar,

Thank you for the details.
I tried to reproduce your issue on windows 10 with workbench 8.0.25 using the stored procedure provided but I am not seeing any issues at my end.
Please upgrade to 8.0.25 and report us back if the issue still exists in latest version. Thanks.

Regards,
Ashwini Patil
[17 Jul 2021 0:33] Michael Aguilar 
I just updated to the new Workbench version and same issue. I am attaching a private video replicating the issue, hope this helps.
[20 Jul 2021 12:23] MySQL Verification Team 
Hello Michael Aguilar,

Thank you for the feedback.
I followed exact steps as you mentioned but I am not seeing any issues at my end. Please see the screenshot attached.

Regards,
Ashwini Patil
[20 Jul 2021 12:25] MySQL Verification Team 
8.0.25 test results

Attachment: 104320_results.png (image/png, text), 160.68 KiB.
[20 Jul 2021 15:54] Michael Aguilar 
I've just updated to the 8.0.26 version, and same issue.
Now I am getting this errors in the Event Viewer:

Faulting application name: MySQLWorkbench.exe, version: 8.0.26.0, time stamp: 0x60db0058
Faulting module name: mysqlcppconn-9-vs14.dll, version: 0.0.0.0, time stamp: 0x60d5f5f2
Exception code: 0x80000003
Fault offset: 0x0000000000099d22
Faulting process id: 0x4f5c
Faulting application start time: 0x01d77d7f323b5175
Faulting application path: C:\Program Files\MySQL\MySQL Workbench 8.0 CE\MySQLWorkbench.exe
Faulting module path: C:\Program Files\MySQL\MySQL Workbench 8.0 CE\mysqlcppconn-9-vs14.dll
Report Id: fbd0ba37-6261-445f-810b-6596665b4299
Faulting package full name: 
Faulting package-relative application ID: 

--------------------------

Fault bucket 2203936892809120608, type 4
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
P1: MySQLWorkbench.exe
P2: 8.0.26.0
P3: 60db0058
P4: mysqlcppconn-9-vs14.dll
P5: 0.0.0.0
P6: 60d5f5f2
P7: 80000003
P8: 0000000000099d22
P9: 
P10: 

Attached files:
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERFB74.tmp.dmp
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERFC6F.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERFC80.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERFC86.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERFC96.tmp.txt

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_MySQLWorkbench.e_367fc41f390e7de2e35fe86cc942473130de_075a4268_5f114829-19b4-4c7b-8ebe-a7c768798799

Analysis symbol: 
Rechecking for solution: 0
Report Id: fbd0ba37-6261-445f-810b-6596665b4299
Report Status: 268435456
Hashed bucket: 1b1eb3f5487d5450ae95f4ed53440b60
Cab Guid: 0