MySQL Bugs: #60248: Workbench crashes on splash page. W7 64 Alienware M15x

Bug #60248	Workbench crashes on splash page. W7 64 Alienware M15x
Submitted:	25 Feb 2011 8:32	Modified:	6 Jun 2011 14:00
Reporter:	Adam T. Janes	Email Updates:
Status:	Can't repeat	Impact on me:	None
Category:	MySQL Workbench	Severity:	S1 (Critical)
Version:	5.2.31a, 5.2.32	OS:	Windows (Windows 7 64 on Alienware m15x)
Assigned to:		CPU Architecture:	Any
Tags:	crashes, MySQL, windows 7 64, workbench

File:	Maximum allowed size is 50MB.
Description:
Privacy:

If the data you need to attach is more than 50MB, you should create a compressed archive of the data, split it to 50MB chunks, and upload each of them as a separate attachment.

To split a large file:

On *nix platforms use the split command e.g. split -b 50MB <my_large_archive> <my_split_archive_prefix>
On windows use WinZip or a similar utility to split the large file

.NET Verifier log (zipped, decompressed is too large)

Attachment: setupverifier_main_03-04-11_08.33.07.txt.zip (application/zip, text), 39.67 KiB.

Win7 Event Viewer log

Attachment: Workbench launch failure.evtx (application/octet-stream, text), 68.00 KiB.

.net verification file

Attachment: setupverifier_main_03-04-11_22.00.42 (text/plain), 470.36 KiB.

Here is my system info

Attachment: SystemInfo.pdf (application/pdf, text), 40.49 KiB.

Still having same problem with 5.2.32

Attachment: workbench crash.jpg (image/pjpeg, text), 25.71 KiB.

Crash event log after updating to 5.2.33b

Attachment: Workbench launch failure.evtx (application/octet-stream, text), 68.00 KiB.

Crash event log, 5.2.33b, using -swrendering option

Attachment: Workbench launch failure.evtx (application/octet-stream, text), 68.00 KiB.

Launch attempt after installing Python 3.2, 32-bit

Attachment: Workbench launch failure.evtx (application/octet-stream, text), 68.00 KiB.

Launch attempt after installing Python 3.2, 64-bit

Attachment: Workbench launch failure 64.evtx (application/octet-stream, text), 68.00 KiB.