MySQL Bugs: #20840: division by zero; Acces violation

Bug #20840	division by zero; Acces violation
Submitted:	4 Jul 2006 3:38	Modified:	4 Jul 2006 13:10
Reporter:	mike wilson	Email Updates:
Status:	Can't repeat	Impact on me:	None
Category:	MySQL Query Browser	Severity:	S3 (Non-critical)
Version:	1.1.20	OS:	Windows (XP SP2)
Assigned to:		CPU Architecture:	Any

Description:
when I try to connect to a MySQL database 5.0.19 via the Query Browser version 1.1.20 it imitally comes up with the browser but instead of a result tab it shows the desktop; at the bottom it says "dvision by zero"
If I click File-> New Query Tab it gives a Result tab but a tthe bottom it says "Access viollation at address 005BAF53 in Module 'MySQLQueryBrowser.exe'. Read of address 000002C8"
I am unable to submit a query via the Query Brwoser; however I can browse the schemas and see the tables and fields.
After reading Bug #17209 it seems the same but the access violation adress is different.

How to repeat:
open Query Browser

Suggested fix:
??

Shows Divide By Zero Error

Attachment: image002.jpg (image/jpeg, text), 48.41 KiB.

Shows Access Violation

Attachment: image002.jpg (image/jpeg, text), 16.38 KiB.

I reinstalled 1.1.20 and got the same reults so I installed an older version 1.1.15, it's the only older one I have.
I got similar results, still the divide by zero error but I got the area where you are supposed to type the query text; however I can't type anything into the box.
This was all working about a month ago, I was able to use 1.1.20 to query my database that I just upgrade from 4.1 to 5.0.
I've been busy with other things and I just tried it again tonight with these wierd results.
I've done nothing to the MySQL DB nor the Query Brower and I don't know what has has changed on my machine to make this happen.

ok, all seems well now, I rebooted and reinstalled 1.1.20 and it is working fine.
I had been playing Civilization III for 5 hours before it started up the Query Browser, it is the only thing I can think off.
Why that gmae would have an effect on the Query Browser I don't know.
BTW I tried the Admin while this was going on and it worked fine.
Because of this I've changed the severity from S1 to S3.
It seems an odd bug for someone to reproduce and research but it also seems odd the the Query Browser acted this way.
Sorry to have wasted anyone's time.

The access violation looks like it came from an exception in the query browser's HandleIdle() function.  There's nothing in the sql editor, so I'm checking if I can reproduce this violation.  Will post back soon.

I couldn't reproduce it.  I check the code and it seems the cause of the access violation is the missing Query Editor section in your screenshot.  Perhaps it wasn't created/initialized due to lack of resources?  If you can get the Query Editor to vanish again then the access violation might re-occur.

I open and closed the Browser 5 diferent times, all with the same result, the divide by zero and access violation, until I rebooted

I've experienced this issue as well, it happened out of the blue after going a while without a reboot.  One thing that hasn't been mentioned yet: after creating a new query tab the cpu goes to 100% utilization until the application is closed.