MySQL Bugs: #32892: MySQL Query Browser Crashes on Mac OS X Leopard

Bug #32892	MySQL Query Browser Crashes on Mac OS X Leopard
Submitted:	1 Dec 2007 5:04	Modified:	8 Sep 2008 3:33
Reporter:	Daniel Zimmerman	Email Updates:
Status:	Can't repeat	Impact on me:	None
Category:	MySQL Query Browser	Severity:	S1 (Critical)
Version:	5.0r12	OS:	MacOS (10.5/10.5.1)
Assigned to:		CPU Architecture:	Any

Description:
MySQL Query Browser crashes on Mac OS X Leopard 10.5 or 10.5.1, on both PPC and Intel platforms. A crash log is attached.

How to repeat:
Attempt to launch MySQL Query Browser.

Suggested fix:
Unknown; perhaps a recompile with the new toolchain will do it.

Unable to repeat on Mac OS X client 10.5.1 intel, using MySQL Query Browser 1.2.12.

How far in startup do you get, do you see the 'connect' dialogue box?

It shows the dialog box, but the UI is completely unresponsive, and nearly immediately (after a brief pause) a crash report, like the one attached to this bug, is generated. This is the case on every Mac OS X 10.5 or 10.5.1 machine I have tried on, and it is indeed version 1.2.12 that I tried. I have tried starting with a clean slate by deleting all my MySQL-related preferences, just in case something old was interfering with the operation of the app, but that didn't help.

MySQL Query Browser crashes for me on OSX 10.5.1 in regular fashion - it has never worked.

I see the Connect Box for about 3 seconds and then it disappears with the crash.  Admin works just fine.

Add to previous comment by me:
I'm on an Intel macbook pro; and it was after a fresh install of 5.0r12.

the same for me, on a MacBookPro with Leopard, Query Browser never worked
--claudio

Bug #35849 was marked as duplicate of this one.

Thank you all for the feedback.

We were still not able to repeat the problem on our side.

And how hard have you been trying? Have you asked for crash reports (or other information) from any of the other people who have reported it, to try to determine the common elements of the failures? Obviously we're not imagining the problem... and we've now gone 6 months without having a working MySQL Query Browser on Mac OS X 10.5.

Same problem here.

Leopard Clean install (in french)

Mac OS X 10.5.2
java version "1.5.0_13"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_13-b05-237)
Java HotSpot(TM) Client VM (build 1.5.0_13-119, mixed mode, sharing)

On a iMac Intel 2.4Ghz Core 2 Duo with 2GB of RAM.

Quit just after launching it. :(

I have the same issue but only on a remote database running v5.0.51
The logon box closed after successful logon, but the main window does not appear to load.
The process is however active.

Connecting to remote datababase 5.0.51 on AIX 5.2 causes the error
Connecting to remote database 4.1.13 on FreeBSB works fine
Connecting to local database 5.0.37 on Linux works fine

Standard Slackware 12 build
mysql-gui-tools-5.0r12-linux-i386
gtk+2-2.10.13

Could it be database server version specific (or perhaps OS)?
Will attempt to install an older version on AIX to test.

Since my bug #37434 has been marked as a duplicate of this one (probably true) I just wanted to chime in that for me this is an Applescript bug within Query Browser. I had Default Folder X running and until I excluded Query Browser it crashed shortly after launching every time.

Rather than repost all my notes please refer to #37434. Below are my instructions to reproduce the problem.

How to repeat:
You can run Default Folder X as I did, but the developer sent me instructions to reproduce
the issue using just Applescript (showing that it's not a Default Folder X problem)

1. Run MySQL Query Browser

2. Run Script Editor (it's in /Applications/AppleScript/).

3. In Script Editor, paste this script into the window and click the "Run" button:
	tell application "MySQL Query Browser"
		beep
	end tell

MySQL Query Browser will promptly crash, just as it did when Default Folder X was running.
 The reason for this is that Script Editor does the same thing Default Folder X does - it
tells MySQL Query Browser to load its scripting additions.  This triggers a bug in it that
causes it to crash.

In the future, when marking things as a duplicate, note the status of the bug. #37434 has been verified as a bug where as this one hasn't so this should probably been marked as a duplicate of 37434 instead of the other way around.

I agree, they should have noted the status (I missed it myself, on my every-few-months search to see if anybody had addressed this issue). I tried the same solution (excluding from Default Folder X) and, in fact, it works for me too. So my sincere thanks for figuring out what's going on (though it seems strange that nobody could figure it out from the crash log, in the first place - including me - since it crashed in CFData in a call from within com.apple.openscripting). In any event, hopefully it will be addressed soon.

On my system (MacBook C2D 2.0GHz, 2GB), MySQL Query Browser would unexpectedly quit and Console.app (under "Console Messages) would report an error trying to load bookmarks.xml from the ~/Library/Application Support/MySQL/QueryBrowser folder.

I recently installed Default Folder X, and adding MySQL Query Browser to the exclusion list in DFX solved the crashing problem.

Mac 10.5.5
Mysql Browser 1.2.12

Mysql Browser crashes a lot for no specific reason.  I have used Navicat and it has not crashed on my once.
How can they release such an unstable product !!  
Does Mysql want to follow MS path?

It was working on 10.5.5, now, after upgrading to 10.5.6, it's crashing shortly after launch

I'm having the same problem here with both Query Browser and Administrator. They both crash after a little while, particularly when I'm editing tables etc. Not only is it annoying, but it's making both unusable.

I have Mac OS X v10.5.6

This was a new Mac, new build about 12 months ago. Over that period Admin and QB were never installed. I installed it in September 2008. It worked fine for a while, then one day, i try to launch QB and i get the Failed to Launch error.

I have tried an older version of the Admin and QB but i get the same problem. 

Admin works fine.

Well, another more to the list.

I'm having crashes really often. So maybe I could be one source to get a good report of the error.
Laptop fully updated. MySQL QB 1.2.12
It happens in two Macbook Pro computers I'm using. Actually in one (new Macbook Pro 15") much more than on the other one (previous version Macbook Pro 17")

Error log:
Jun 19 00:57:39 Didac-17 ReportCrash[7162]: Formulating crash report for process MySQL Query Browser[7027]
Jun 19 00:57:40 Didac-17 com.apple.launchd[125] ([0x0-0xb80b8].com.mysql.QueryBrowser[7027]): Exited abnormally: Segmentation fault
Jun 19 00:57:41 Didac-17 ReportCrash[7162]: Saved crashreport to /Users/didac_gil_9/Library/Logs/CrashReporter/MySQL Query Browser_2009-06-19-005737_Didac-17.crash using uid: 501 gid: 20, euid: 501 egid: 20

Contact to my mail if I could help to recreate the error and provide a deep error log. (I would do it if I knew how to)