MySQL Bugs: #6836: MySQL Administrator access violation when trying to exit

Bug #6836	MySQL Administrator access violation when trying to exit
Submitted:	26 Nov 2004 5:50	Modified:	26 Dec 2004 16:29
Reporter:	Derek Kalweit	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL Administrator	Severity:	S1 (Critical)
Version:	1.0.14	OS:	Windows (Windows 2003)
Assigned to:		CPU Architecture:	Any

Description:
MySQL Administrator will not close. I get an access violation instead:

"Access violation at address 0058C3CC in module 'MySQLAdministrator.exe'. Read of address 00000008"

How to repeat:
Use a Windows 2003 box(not sure if this is required, but I bet it's probably the cause, knowing W2K3...)

1. Start MySQL Administator and connect to localhost as root
2. Close
3. Repeat 1 and 2 until it happens. I've had it not happen; Try going through some tabs, including the Health tabs particularly if you can't get it to happen.

Suggested fix:
It looks like someone's doing some pointer arithmetic with a NULL pointer? +8? I haven't looked at code. Right now, I'm killing the process through the task manager when I need it to go away.

Hello,

Thank you for the report, but I wasn't able reproduce "Access violation".
We need a repeatable test case, i.e. exact set of actions that help us to reproduce this error.
You mentioned about "Helth" tabs. Do you have any custom graph there?

Victoria, did you test this on Windows 2003? Maybe it only happens in a Terminal Services/Remote Desktop session as I'm running? Do you have a tracing feature so I can create a trace log and add that to this case after re-creating the error? I'd see about setting up an environment to debug the problem to give you the exact line of code, but the server is a production server that I don't want to introduce that to. I don't have anything custom(like health charts) setup in MySQL Administrator-- just a basic install, one new user, and one new schema... Thanks.

-- 
Derek

No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".