MySQL Bugs: #52949: Workbench Visual C++ Library run-time errors

Bug #52949	Workbench Visual C++ Library run-time errors
Submitted:	19 Apr 2010 16:56	Modified:	1 Sep 2010 10:32
Reporter:	Garen Parham	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Workbench	Severity:	S1 (Critical)
Version:	5.2.17 Revision 5565, 5.2.19, 5.2.20,5.2.22, 5.2.25	OS:	Windows
Assigned to:	Alfredo Kojima	CPU Architecture:	Any
Tags:	crash

Description:
After upgrading from 5.2.15, workbench causes Windows XP to reboot if I open it standalone from -> Start -> Programs -> MySQL -> MySQL WorkBench 5.2 OSS.

If I open up a .mwb file, it launches an error dialog titled "Microsoft Visual C++ Runtime Library" with the message:

Runtime Error!

Program: C:\Pro...

R6034
An application has made an attempt to load the C runtime library incorrectly. Please contact the application's support team for more information.

The dialog's only option is OK.  After pressing OK, two more instances of the same dialog pop up.  After hitting OK to all three, Workbench opens up with my .mwb file displayed.

On Windows 7 x64 I get the same run-time error (R6034) on the most recent release - 5.2.19 on startup.

How to repeat:
Install software and run it.

Hi Garen,

could you try again with latest release (5.2.19) to check if the problem still occurs?
thanks in advance

Still happens with 5.2.19.

Screenshot of error

Attachment: Microsoft Visual C++ Runtime Library 452010 43501 PM.jpg (image/jpeg, text), 28.39 KiB.

Please, send the results from Help > System Info menu item.

Sure:

MySQL Workbench SE for Windows version 5.2.19

Cairo Version: 1.8.8

Rendering Mode: OpenGL is available on this system, so OpenGL is used for rendering.

OpenGL Driver Version: 1.5.0 - Build 7.14.10.4943

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

CPU: 2x Intel(R) Core(TM)2 CPU          6400  @ 2.13GHz�������p�@p�, 3.0 GiB RAM

Video adapter info:

Adapter type: Intel(R)  Q965/Q963 Express Chipset Family

Chip Type: Intel(R) GMA 3000

BIOS String: Intel Video BIOS

Video Memory: 262144 KB

Please, check with a newer version, 5.2.20, and inform about the results.

Same results with 5.2.20

Please try with oss config instead of se config.

Not sure why it used to say "SE", but I've always been using the free OSS version.  

The issue is still present in 5.2.20 Beta where my System Info says:

MySQL Workbench OSS for Windows version 5.2.20

Cairo Version: 1.8.8

Rendering Mode: OpenGL is available on this system, so OpenGL is used for rendering.

OpenGL Driver Version: 1.5.0 - Build 7.14.10.4943

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

CPU: 2x Intel(R) Core(TM)2 CPU          6400  @ 2.13GHz��� �� ��ؙ�;ؙ, 3.0 GiB RAM

Video adapter info:

Adapter type: Intel(R)  Q965/Q963 Express Chipset Family

Chip Type: Intel(R) GMA 3000

BIOS String: Intel Video BIOS

Video Memory: 262144 KB

I just ran into the same issue on my installation.  Now, the interesting part was that it was running fine until I worked on a C++ project in VS2008.  Needed to compile curl for pycurl.

MySQL Workbench OSS for Windows version 5.2.20

Cairo Version: 1.8.8

Rendering Mode: OpenGL is available on this system, so OpenGL is used for rendering.

OpenGL Driver Version: 2.1.8874

OS: Microsoft Windows 7 Ultimate Edition (build 7600), 32-bit

CPU: 2x Intel(R) Core(TM)2 Duo CPU     P8600  @ 2.40GHz|���8���;�8��, 2.5 GiB RAM

Video adapter info:

Adapter type: Mobile Intel(R) 4 Series Express Chipset Family

Chip Type: Mobile Intel(R) 4 Series Express Chipset Family

BIOS String: Intel Video BIOS

Video Memory: 1060878 KB

This happened to me too, after I updated to 5.2.21 RC. Uninstalling and manual removing left files didn't help. I constantly got this R6034 error dialog. But it didn't crash I can still use it. DLL confusion?

MySQL Workbench OSS for Windows version 5.2.21

Cairo Version: 1.8.8

Rendering Mode: OpenGL is available on this system, so OpenGL is used for rendering.

OpenGL Driver Version: 2.1.9116

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

CPU: 2x Intel(R) Pentium(R) 4 CPU 3.00GHz, 2.0 GiB RAM

Video adapter info:

Adapter type: ATI Radeon HD 3400 Series 

Chip Type: ATI Radeon Graphics Processor (0x95C5)

BIOS String: 113-AB37400-104

Video Memory: 524288 KB

I just tried 5.2.22RC2 and this still happens.

My situation is when the startup splash window shows up , 2 or 3 R6034 error message dialog would pop up.

I have tried reinstalling WB, removing all data files under "Application Data\" to no avail.

Though it looks like it still can run, but it still makes me worry about any unknown potential problems.

I'd like to help out here. Is there anyway to generate any trace output so you can look into this ?

ywliu

I also have the same errors.

It was working fine for me on Windows, until I installed "paramiko" (which is a Python library that deals with SFTP).   This smells like DLL versioning/confusion.

I agree, this problem sounds like one or more libraries used from a wrong path. WB comes with some third-party stuff and Microsoft DLLs, so it would be good if you could check which DLL it is actually using. For this download Process Explorer from Microsoft (http://technet.microsoft.com/en-us/sysinternals/bb896653.aspx) and examine WB while it is running. It can show you which DLLs are loaded. If you see something unexpected (like DLLs not from the WB folder or typical system libraries from the Windows folder) please let us know.

Also check your system search path. Usually DLLs in the app folder are found first but I have seen this not always be the case. Thank you.

This reminds me of ActiveState Python 2.6 I installed on my computer.

After looking into the DLLs with Process Explorer, I notice several .pyd files outside WB and Windows system paths are loaded :

C:\Python26\DLLs\_hashlib.pyd
C:\Python26\DLLs\_socket.pyd
C:\Python26\DLLs\_ssl.pyd
C:\Python26\DLLs\select.pyd

And after renaming C:\Python26\ to something else to let WB fail to read DLLs from Python26, the VC++ runtime errors are gone.

Now is there anyway to avoid this, at least in my case, Python DLL confusion ? Removing my Python distribution is not an option....:P

ywliu

Hi

I have also been experiencing this error, and I also have Active State Python installed.

Andrew

I'm experiencing this same issue: get the error 3 times then the app starts up anyway.  I also have ActiveState Python installed.  Renaming the Python26 directory allows Workbench to start without error.  I'm on XP Pro SP3

So, we've found the problem.  The solution would seem to be for Workbench to use its own copy of the C runtime DLL instead of loading it off the path.

Thank you for the feedback.

Verified as described: having ActivePython installed leads to  Runtime errors at startup.

Bug #55490 has been marked as duplicate of this one

fixed

fix confirmed in repository

See also bug #55725

An entry has been added to the 5.2.27 changelog:

MySQL Workbench caused Windows XP to reboot if launched from Start, Programs, MySQL, MySQL WorkBench 5.2 OSS.

If a MySQL Workbench model file (.mwb) was opened directly, an error dialog titled Microsoft Visual C++ Runtime Library was displayed with the message:

R6034
An application has made an attempt to load the C runtime library incorrectly. Please
contact the application's support team for more information.

The dialog's only option was OK. After clicking OK, two more instances of the same dialog were displayed. After clicking OK for all three, MySQL Workbench opened with the model file displayed.

On Windows 7 x64 the same run-time error (R6034) occurred.