MySQL Bugs: #7767: Segmentation fault

Bug #7767	Segmentation fault
Submitted:	10 Jan 2005 13:01	Modified:	1 Mar 2005 23:28
Reporter:	Mustafa Incel	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Query Browser	Severity:	S3 (Non-critical)
Version:	1.1.5	OS:	Ferdora Core 3
Assigned to:	Alfredo Kojima	CPU Architecture:	Any

Description:
Hello,
Sometimes, when i try to execute simple select queries, my Query Browser exits and i get segmentaion fault in my gnome terminal. 

[mincel@localhost bin]$ ./mysql-query-browser
./mysql-query-browser: line 9:  5614 Segmentation fault      $MYPATH/mysql-query-browser-bin
[mincel@localhost bin]$ ./mysql-query-browser
./mysql-query-browser: line 9:  5625 Segmentation fault      $MYPATH/mysql-query-browser-bin
[mincel@localhost bin]$ ./mysql-query-browser
./mysql-query-browser: line 9:  5640 Segmentation fault      $MYPATH/mysql-query-browser-bin

How to repeat:
Double click on a table and execute the query.

I wasn't able to repeat this.  Can you tell us exactly what queries did you execute and if possible a set of steps that will successfully reproduce this problem ?

thanks!

Hi,
When i execute a simple select statenment like 'SELECT * FROM user u', SOMETIMES, i get Segmentation fault. I didn't test for other SQL statements. 
For example in sidebar, double click on 'mysql' database and then 'user' table, you'll get the above select statement. If i execute this statement 2-3 times, i get the error.
NOTE: I have installed all the available updates.

Same thing happens for me on Fedora Core 3 (MySQL Query browser 1.1.5).  Example error message:

/home/gavin/apps/mysql-query-browser/bin/mysql-query-browser: line 9:  5952 Segmentation fault      $MYPATH/mysql-query-browser-bin

Steps to reproduce:
A number of actions seem to cause this, but most often it happens when you build a query, execute it and then you hit execute again. Often happens if you've just editted the query or changed it and you hit execute button. Sometimes happens when hitting the refresh button.

Simplest example would be:
1) Start the app
2) Keep on clicking execute until it segfaults. 3-4 clicks required on my system before segfault.

Thanks, I was just able to reproduce this.

This bug was classified as Non-Critical.  I don't agree with this at all.  The program is pretty much unusable with this bug.  Needs to be upgraded.

I agree with this bug's serverity being understated.  I can't use this application at all either.

There are numerous ways to get a segmentation fault with this program and all seem to be after a mouse click.  To me, this makes the application completely unstable.

I also agree that to classify this bug as non-critical is an understatement. The fact that a single click of the mouse causes a seg fault makes an otherwise nice product almost un-usable. What criteria determine the severity status?

This bug has been finally fixed (was hard to track down). The next release should (due today or tomorrow) work better much better.