MySQL Bugs: #65056: Workbench 5.2.39 Crashes On Start

Bug #65056	Workbench 5.2.39 Crashes On Start
Submitted:	20 Apr 2012 14:46	Modified:	27 Jul 2012 7:53
Reporter:	Bryce Byrd	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Workbench	Severity:	S1 (Critical)
Version:	5.2.39	OS:	Windows (XP Pro SP3)
Assigned to:		CPU Architecture:	Any

Description:
I uninstalled a working version of 5.2.? (don't remember which one now) and installed 5.2.39. Before I installed it i downloaded and installed both of the prerequisites (visual C++ x86 redist and .Net 4.0 client).

When I run it I get

Event Type: Error
Event Source: .NET Runtime
Event Category: None
Event ID: 1026
Date: 2012-04-19
Time: 13:23:56
User: N/A
Computer: REDACTED
Description:
Application: MySQLWorkbench.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.AccessViolationException
Stack:
at <Module>.base.Logger.log(LogLevel, SByte*, SByte*, ...)
at MySQL.Workbench.Logger.LogInfo(System.String, System.String)
at MySQL.GUI.Workbench.Program.PrintInitialLogInfo()
at MySQL.GUI.Workbench.Program.Main(System.String[])

The program has been successfuly writing the wb.log during startup, so accessing that file isn't it. Here's the wb.log...

13:31:50 [INF][ Workbench]: Starting up Workbench
13:31:50 [INF][ Workbench]: Current environment:
Command line: "C:\Program Files\MySQL\MySQL Workbench 5.2 CE\MySQLWorkbench.exe"
CurrentDirectory: C:\Program Files\Mozilla Firefox
HasShutdownStarted: False
OSVersion: Microsoft Windows NT 5.1.2600 Service Pack 3
SystemDirectory: C:\WINDOWS\system32
TickCount: 160363015
UserInteractive: True
Version: 4.0.30319.261
WorkingSet: 27574272

How to repeat:
N/A

Suggested fix:
Hey Bryce,

since the work environment is successfully logged there must be something with your environment variables (which would be the next item to be logged). The crash happens in the logger itself so probably the string passed to it contains something weird. Can you file a bug report (http://bugs.mysql.com) and attach the output of your SET command (run this on a command line). You can make this private in the bug tracker, so your env values are kept save.

Mike

Mike Lischke, MySQL Developer Tools
Oracle Corporation

I couldn't repeat on Xp Home Edition SP 3:

MySQL Workbench CE for Windows version 5.2.39  revision 8757

Configuration Directory: C:\Documents and Settings\miguel\Dados de aplicativos\MySQL\Workbench

Data Directory: C:\Arquivos de programas\MySQL\MySQL Workbench 5.2 CE

Cairo Version: 1.8.8

OS: Microsoft Windows XP Home Edition Service Pack 3 (build 2600)

CPU: AMD Phenom(tm) 9650 Quad-Core Processor, 1.2 GiB RAM

Active video adapter (0): VM Additions S3 Trio32/64

Installed video RAM: 8 MB

Current video mode: 1600 x 931 x 4294967296 cores

Used bit depth: 32

Driver version: 013.548

Installed display drivers: vpc-s3.sys

Current user language: Português (Brasil)

I observe this crash on Win 7 64 bit

I also came across this bug. Per the suggestion at <http://forums.mysql.com/read.php?152,526320,527055#msg-527055> I removed the percent signs from environment variables names. This fixed the issue.

Fixed as of Workbench 5.2.41, and here's the changelog entry:

Using the '%' character within environment variables could cause
MySQL Workbench to crash.