MySQL Bugs: #80130: MySQL Workbench hangs or crashed after updating a row

Bug #80130	MySQL Workbench hangs or crashed after updating a row
Submitted:	24 Jan 2016 20:05	Modified:	2 Feb 2016 8:00
Reporter:	Steve Fatula	Email Updates:
Status:	Duplicate	Impact on me:	None
Category:	MySQL Workbench: SQL Editor	Severity:	S2 (Serious)
Version:	6.3.6	OS:	MacOS (10.11.3)
Assigned to:		CPU Architecture:	Any
Tags:	crash, hang

Description:
I bring up a small table via select * from tablename. I go into the grid, change a single columns value in a single row. I click apply, it says it was successfully applies. Then, the problem starts, I click the OK box and it hangs. Been doing this for many months, including the previous Mac OSX 10.10. Also, the previous workbench version. Sometimes, it actually crashes after the update. So, I end up having to force quit the application. I am sending the results of the force quit as it may be useful in follow up attachment.

How to repeat:
This does not always seem to happen, but, does happen at least once per day.

Force quit trace data

Attachment: Workbench Hang 80130.txt (text/plain), 1.46 MiB.

Crash Example

Attachment: Workbench Crash 80130.txt (text/plain), 106.36 KiB.

I couldn't repeat this issue. Please check if there is a specific step by step process (kind of table, size result data, specific column, etc). Thanks.

Well, I can tell you it's an IP over SSH connection method, so, via tunnel, and, using SSH key file (that has made some difference in the past on other bugs). 

It does not happen every time, it does happen once or more per day. So, I also cannot do one or two commands and expect it to fail, it will not typically (though sometimes, it happens first try). The point of the crashlog was to point you to the piece of code causing the issue. 

The host mysql server is 5.5.44, if that matters. 

Machine updates over 10 million rows per day across the database just fine, no issues at all. I can update the record via mysql command line just fine, no errors or issues. However, if I select * from tablename, go to a row and column, type in a new value, tab out, and hit apply, it does update, and then hangs or aborts. If i simply do the update statement that MySQL workbench executes to update that row (copy and paste it), it also works fine, no hang, nothing. It's only when using the grid to type and update records. All other functions work fine, and I use the product 8 hours a day on z dozen or so hosts. 

So, not sure what else I can do. Is there a debug feature of workbench that might help? Some sort of workbench log file? 

I suppose I might be able to give you remote access to the database so you can see for yourself? Though, not sure how I can securely do so?

Thank you for the feedback. I was able to repeat on Windows updating a row.

>	ntdll.dll!00007ff973fb47b0()	Unknown
 	ntdll.dll!00007ff973fc49d9()	Unknown
 	ntdll.dll!00007ff973fb890a()	Unknown
 	grt.dll!00007ff93ab76b19()	Unknown
 	wbpublic.be.dll!00007ff933c3e561()	Unknown
 	wbpublic.be.dll!00007ff933c3e6fd()	Unknown
 	wbpublic.be.dll!00007ff933d41aec()	Unknown
 	wbpublic.be.dll!00007ff933d43612()	Unknown
 	wbpublic.be.dll!00007ff933d435d3()	Unknown
 	wbpublic.be.dll!00007ff933d4359d()	Unknown
 	wbpublic.be.dll!00007ff933d4318f()	Unknown
 	wbpublic.be.dll!00007ff933c596a9()	Unknown
 	wbpublic.be.dll!00007ff933c57183()	Unknown
 	wbpublic.be.dll!00007ff933c59127()	Unknown
 	wbpublic.be.dll!00007ff933c58396()	Unknown
 	libglib-2.0-0.dll!0000000068627881()	Unknown

Thanks, I was going to do Windows next actually if you needed it. Good to hear it fails there also. Surprised no one else had reported. I've actually had this for many many months, if not longer (don't recall). Just never got around to reporting it.

<cut>
'MySQLWorkbench.exe' (Win32): Loaded 'C:\Windows\Microsoft.NET\Framework64\v4.0.30319\clr.dll'. Cannot find or open the PDB file.

s\MySQL\MySQL Workbench 6.3 CE\python\DLLs\_socket.pyd'. Cannot find or open the PDB file.
'MySQLWorkbench.exe' (Win32): Loaded 'C:\Windows\System32\nlaapi.dll'. Cannot find or open the PDB file.
'MySQLWorkbench.exe' (Win32): Loaded 'C:\Windows\System32\NapiNSP.dll'. Cannot find or open the PDB file.
'MySQLWorkbench.exe' (Win32): Loaded 'C:\Windows\System32\pnrpnsp.dll'. Cannot find or open the PDB file.
'MySQLWorkbench.exe' (Win32): Loaded 'C:\Windows\System32\dnsapi.dll'. Cannot find or open the PDB file.
'MySQLWorkbench.exe' (Win32): Loaded 'C:\Windows\System32\nsi.dll'. Cannot find or open the PDB file.
'MySQLWorkbench.exe' (Win32): Loaded 'C:\Windows\System32\winrnr.dll'. Cannot find or open the PDB file.
'MySQLWorkbench.exe' (Win32): Loaded 'C:\Program Files\Bonjour\mdnsNSP.dll'. Cannot find or open the PDB file.
'MySQLWorkbench.exe' (Win32): Loaded 'C:\Windows\System32\IPHLPAPI.DLL'. Cannot find or open the PDB file.
'MySQLWorkbench.exe' (Win32): Loaded 'C:\Windows\System32\wshbth.dll'. Cannot find or open the PDB file.
'MySQLWorkbench.exe' (Win32): Loaded 'C:\Program Files\MySQL\MySQL Workbench 6.3 CE\python\site-packages\Crypto\Random\OSRNG\winrandom.pyd'. Cannot find or open the PDB file.
'MySQLWorkbench.exe' (Win32): Loaded 'C:\Program Files\MySQL\MySQL Workbench 6.3 CE\python\site-packages\Crypto\Util\_counter.pyd'. Cannot find or open the PDB file.
'MySQLWorkbench.exe' (Win32): Loaded 'C:\Program Files\MySQL\MySQL Workbench 6.3 CE\python\site-packages\Crypto\Cipher\_AES.pyd'. Cannot find or open the PDB file.
6.3 CE\wb.printing.wbp.be.dll'. Cannot find or open the PDB file.
'MySQLWorkbench.exe' (Win32): Loaded 'C:\Windows\System32\wbem\wbemprox.dll'. Cannot find or open the PDB file.
'MySQLWorkbench.exe' (Win32): Loaded 'C:\Windows\System32\wbemcomn.dll'. Cannot find or open the PDB file.
'MySQLWorkbench.exe' (Win32): Loaded 'C:\Windows\System32\wbem\wbemsvc.dll'. Cannot find or open the PDB file.
'MySQLWorkbench.exe' (Win32): Loaded 'C:\Windows\System32\wbem\fastprox.dll'. Cannot find or open the PDB file.
'MySQLWorkbench.exe' (Win32): Loaded 'C:\Windows\System32\UIAutomationCore.dll'. Cannot find or open the PDB file.
'MySQLWorkbench.exe' (Win32): Loaded 'C:\Windows\System32\userenv.dll'. Cannot find or open the PDB file.
'MySQLWorkbench.exe' (Win32): Loaded 'C:\Windows\System32\sxs.dll'. Cannot find or open the PDB file.
'MySQLWorkbench.exe' (Win32): Loaded 'C:\Windows\assembly\NativeImages_v4.0.30319_64\Accessibility\80895d305dc304d953d3ce241b9a556c\Accessibility.ni.dll'. 
'MySQLWorkbench.exe' (Win32): Loaded 'C:\Windows\System32\oleacc.dll'. Cannot find or open the PDB file.
'MySQLWorkbench.exe' (Win32): Loaded 'C:\Windows\System32\rasadhlp.dll'. Cannot find or open the PDB file.
'MySQLWorkbench.exe' (Win32): Loaded 'C:\Windows\System32\edputil.dll'. Cannot find or open the PDB file.
'MySQLWorkbench.exe' (Win32): Loaded 'C:\Windows\System32\urlmon.dll'. Cannot find or open the PDB file.
'MySQLWorkbench.exe' (Win32): Loaded 'C:\Windows\System32\iertutil.dll'. Cannot find or open the PDB file.
'MySQLWorkbench.exe' (Win32): Loaded 'C:\Windows\System32\atlthunk.dll'. Cannot find or open the PDB file.
'MySQLWorkbench.exe' (Win32): Loaded 'C:\Windows\System32\actxprxy.dll'. Cannot find or open the PDB file.
The thread 0x3738 has exited with code 0 (0x0).
Unhandled exception at 0x00007FF973FB47B0 (ntdll.dll) in MySQLWorkbench.exe: 0xC0000026: An invalid exception disposition was returned by an exception handler.

The program '[10824] MySQLWorkbench.exe' has exited with code 0 (0x0).

This is a duplicate of bug 77286