MySQL Bugs: #101081: MySQL Workbench is not starting anymore (python27.dll system crash in event vwr)

Bug #101081	MySQL Workbench is not starting anymore (python27.dll system crash in event vwr)
Submitted:	7 Oct 2020 12:47	Modified:	9 Oct 2020 10:17
Reporter:	Karsten Wutzke	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Workbench	Severity:	S1 (Critical)
Version:	8.0.21	OS:	Windows (10 Pro)
Assigned to:		CPU Architecture:	x86 (64 bit)
Tags:	dll, python, startup

Description:
This is very very similar to

https://bugs.mysql.com/bug.php?id=98207

if not the same.

I just had a running MySQL Workbench 8.0.19 and from one second to the other it failed to re-start.

I reinstalled the latest Visual C++ runtime. I reinstalled the latest 8.0.21. The startup process ends after a second or two. (Windows 10 64bit)

I launched the Windows Event Viewer (Ereignisanzeige in German) and I found two error entries regarding WB. Here are the copied contents:

(Unfortunately this is in German, whoever thinks that localizing error messages and tools is a good thing, this is what you get...)

ERROR #1:

Protokollname: Application
Quelle:        Application Error
Datum:         07.10.2020 14:10:10
Ereignis-ID:   1000
Aufgabenkategorie:(100)
Ebene:         Fehler
Schlüsselwörter:Klassisch
Benutzer:      Nicht zutreffend
Computer:      P71
Beschreibung:
Name der fehlerhaften Anwendung: MySQLWorkbench.exe, Version: 8.0.21.0, Zeitstempel: 0x5eee769a
Name des fehlerhaften Moduls: python27.dll, Version: 2.7.14150.1013, Zeitstempel: 0x5daee72e
Ausnahmecode: 0xc0000005
Fehleroffset: 0x00000000000eacf4
ID des fehlerhaften Prozesses: 0x31a4
Startzeit der fehlerhaften Anwendung: 0x01d69ca2cc5d369d
Pfad der fehlerhaften Anwendung: C:\Program Files\MySQL\MySQL Workbench 8.0 CE\MySQLWorkbench.exe
Pfad des fehlerhaften Moduls: C:\Program Files\MySQL\MySQL Workbench 8.0 CE\python27.dll
Berichtskennung: 023fa997-0fc3-4a49-ac09-0d5442f8e4c2
Vollständiger Name des fehlerhaften Pakets: 
Anwendungs-ID, die relativ zum fehlerhaften Paket ist: 
Ereignis-XML:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Application Error" />
    <EventID Qualifiers="0">1000</EventID>
    <Level>2</Level>
    <Task>100</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2020-10-07T12:10:10.325204200Z" />
    <EventRecordID>74809</EventRecordID>
    <Channel>Application</Channel>
    <Computer>P71</Computer>
    <Security />
  </System>
  <EventData>
    <Data>MySQLWorkbench.exe</Data>
    <Data>8.0.21.0</Data>
    <Data>5eee769a</Data>
    <Data>python27.dll</Data>
    <Data>2.7.14150.1013</Data>
    <Data>5daee72e</Data>
    <Data>c0000005</Data>
    <Data>00000000000eacf4</Data>
    <Data>31a4</Data>
    <Data>01d69ca2cc5d369d</Data>
    <Data>C:\Program Files\MySQL\MySQL Workbench 8.0 CE\MySQLWorkbench.exe</Data>
    <Data>C:\Program Files\MySQL\MySQL Workbench 8.0 CE\python27.dll</Data>
    <Data>023fa997-0fc3-4a49-ac09-0d5442f8e4c2</Data>
    <Data>
    </Data>
    <Data>
    </Data>
  </EventData>
</Event>

ERROR #2:

Protokollname: Application
Quelle:        .NET Runtime
Datum:         07.10.2020 14:10:10
Ereignis-ID:   1026
Aufgabenkategorie:Keine
Ebene:         Fehler
Schlüsselwörter:Klassisch
Benutzer:      Nicht zutreffend
Computer:      P71
Beschreibung:
Anwendung: MySQLWorkbench.exe
Frameworkversion: v4.0.30319
Beschreibung: Der Prozess wurde aufgrund einer unbehandelten Ausnahme beendet.
Ausnahmeinformationen: System.AccessViolationException
   bei <Module>.wb.WBContextUI.init(wb.WBContextUI*, wb.WBFrontendCallbacks*, wb.WBOptions*)
   bei MySQL.Workbench.WbContext.init(MySQL.Workbench.WbFrontendCallbacks, MySQL.Workbench.WbOptions, VoidStrUIFormDelegate)
   bei MySQL.GUI.Workbench.Program.Main(System.String[])

Ereignis-XML:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name=".NET Runtime" />
    <EventID Qualifiers="0">1026</EventID>
    <Level>2</Level>
    <Task>0</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2020-10-07T12:10:10.250774900Z" />
    <EventRecordID>74808</EventRecordID>
    <Channel>Application</Channel>
    <Computer>P71</Computer>
    <Security />
  </System>
  <EventData>
    <Data>Anwendung: MySQLWorkbench.exe
Frameworkversion: v4.0.30319
Beschreibung: Der Prozess wurde aufgrund einer unbehandelten Ausnahme beendet.
Ausnahmeinformationen: System.AccessViolationException
   bei &lt;Module&gt;.wb.WBContextUI.init(wb.WBContextUI*, wb.WBFrontendCallbacks*, wb.WBOptions*)
   bei MySQL.Workbench.WbContext.init(MySQL.Workbench.WbFrontendCallbacks, MySQL.Workbench.WbOptions, VoidStrUIFormDelegate)
   bei MySQL.GUI.Workbench.Program.Main(System.String[])

</Data>
  </EventData>
</Event>

Links to screenshots:

https://ibb.co/KbwwQ18

https://ibb.co/vz0MFgr

https://ibb.co/JBDFSyG

How to repeat:
See description.

Short error:

Name der fehlerhaften Anwendung: MySQLWorkbench.exe, Version: 8.0.21.0, Zeitstempel: 0x5eee769a
Name des fehlerhaften Moduls: python27.dll, Version: 2.7.14150.1013, Zeitstempel: 0x5daee72e
Ausnahmecode: 0xc0000005
Fehleroffset: 0x00000000000eacf4
ID des fehlerhaften Prozesses: 0x31a4
Startzeit der fehlerhaften Anwendung: 0x01d69ca2cc5d369d
Pfad der fehlerhaften Anwendung: C:\Program Files\MySQL\MySQL Workbench 8.0 CE\MySQLWorkbench.exe
Pfad des fehlerhaften Moduls: C:\Program Files\MySQL\MySQL Workbench 8.0 CE\python27.dll

I also tried older versions 8.0.18 and 8.0.12. Same here.

I wonder what caused this to stop working all of a sudden. Maybe the VC redistributable is bugged?

Sorry for the confusion.

I am authoring a plugin in Python that had a syntax error in my plugin module, so it is quite logical that the plugin failed and WB doesn't start up.

Maybe you want to improve that error handling some day.

Again, sorry for that.

Please handle the bug status as you like.

Here's the code that caused this crash:

    for key, value in options:
        if isinstance(value, int)         <-- missing ":"
            Log.error("Key " + key + " has int value: " + options[key])

Yeah. Maybe improve internal plugin error handling.

I don't see why an error in some plugin code should prevent the WB application from starting up at all... it's not very sophisticated.

Hello Karsten Wutzke,

Thank you for clarifying that there was syntax error in your plugin module.
I'm closing this for now.

Regards,
Ashwini Patil

All the coding stuff here quite helpful and we able to explore lots of new things here. I was looking for the material to explore and boost my knowledge glad to have it. Thumbs up with the excellent sharing on https://www.assignmentmasters.co.uk/ about error fixing is thoughtful.