Bug #29321 access violation / thread_cache_size
Submitted: 24 Jun 2007 3:31 Modified: 8 Dec 2008 9:31
Reporter: Jesper Engberg Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Administrator Severity:S3 (Non-critical)
Version:1.2.11 - 1.2.14 OS:Windows (Windows Server 2003 R2 SP2)
Assigned to: Mike Lischke CPU Architecture:Any

[24 Jun 2007 3:31] Jesper Engberg
Description:
On first execution of MySQL Administrator after MySQL Service is started, everything works fine. If i close the Administrator application and start it again i got:

Access violation at address 0042A986 in module 'MySQLAdministrator.exe'. 
Read of address 00000004

Then, everytime i go to "Server Information" i got:

Access violation at address 00602219 in module 'MySQLAdministrator.exe'. 
Read of address 00000057

If i close MySQL Administrator and restart MySQL Service (Net STOP MySQL + Net START MySQL) it works again once.

I have tested both with 1.2.11 and 1.2.12, different on 1.2.11 is address of access violation changed from 00602219 to 00602171

I got the same result using MySQL 5.0.41 and 5.1.19 with my-large.ini as config file. it seams to depend on thread_cache_size, changed it to zero, and then MySQL Administrator works again.

How to repeat:
Install zip-version of MySQL as Service in c:\mysql\ using my-large.ini or my-huge.ini as config file.

start mysql and run mysql administrator, close mysql administrator and run it again.

restart mysql service

start mysql and run mysql administrator, close mysql administrator and run it again.
[26 Jun 2007 19:20] Sveta Smirnova
Thank you for the report.

Which CPU and how much physical RAM does your comouter has?
[26 Jun 2007 21:59] Jesper Engberg
I am running a virtual machine under MS Virtual Server
Cpu: Intel XEON E5310 Quad Core 1.6MHZ
Memory: 1 GB dedicated to the virtual machine
[3 Jul 2007 10:33] Paul Edwards
Im able to reproduce this under a guest in vmware (ESX 3.01 32039). (2.0Ghz Xeon)

It would appear the Server Information page doesn't like being under a virtualised host.
[25 Jul 2007 14:00] Rex Sham
I have the same case on a Win2003 Enterprise SP2 with Athlon XP 2500+ and 1GB Ram...
[19 Aug 2007 21:57] Richard Bard
I am having the same issue.

I am running Windows Server 2003
MySql Version 5.0.41
MySql Administrator 1.2.12
AMD 64 3500+
1 Gig Memory

I have no other issues it seems, but I am able to recreate this by closing and reopening the administrator.

I have not yet run the SP2 update.
[2 Dec 2007 13:18] Sveta Smirnova
Thank you for the report.

Please run Task Manager in time when you run MySQL Administrator and provide screenshots of RAM and CPU usage in time of failure.
[11 Dec 2007 13:36] Maarten Damen
We have the same problem on a server with Windows server 2003 (SP2)
I also had a backup schedule defined, removing the schedule doesn't solve the problem... 
Any news on this bug yet? I see it hasn't been assigned to anyone yet...
[3 Jan 2008 0:00] Bugs System
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".
[10 Feb 2008 17:17] Shimon Klein
We are getting the same error using Win2003 on ESX.  Here is the screen shot requested.
[10 Feb 2008 17:18] Shimon Klein
We are getting the same error using Win2003 on ESX.  Here is the screen shot requested.

Attachment: MySQLServerInformationError.jpg (image/jpeg, text), 344.17 KiB.

[30 May 2008 9:46] Jirka Sedlak
So, is there any solution for this??
[2 Jun 2008 7:36] Claus Topholt
I have exactly the same problem. MySQL is version 5.0.56 sp1 (enterprise trial). MySQL Administrator version is 1.2.12.

I'm running it in an MS virtual server image.
[18 Jun 2008 12:50] MySQL Verification Team
Could you please see if exists something related with the bug http://bugs.mysql.com/bug.php?id=37452?. Thanks in advance.
[18 Jul 2008 23:00] Bugs System
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".
[25 Aug 2008 14:36] Sebastian Oromi
My box is hardware and not VM.

Regards,

Sebastian
[17 Oct 2008 8:18] Tonci Grgin
Jesper, guys.

There is no way I can repeat this using latest Administrator against both local (in VM) or remote (on physical VM host) 5.0.68PB MySQL server. I tried everything but error just does not appear.

Please upgrade to latest version of GUI tools and retest. If it still fails, reopen the bug report and add as much data as possible.
[24 Nov 2008 17:03] Tonci Grgin
There seems to be a problem with ESX here, as my VMServer runs without errors. Please contact VMWare support.
[1 Dec 2008 13:59] Andrii Nikitin
Verified in 1.2.14

Conditions:
1. Windows 2003 Server, SP2

2. VMware build 91891

3. Access using Windows Console 'mstsc /console'

4. Monitored server was Slave 5.1.28 (version number should'n matter much, not sure if being Slave also matters)

5. thread_cache_size should be non-zero. (two restars of MySQLAdministrator may be required after changing this parameter to see the exception).

Exception appears in TAdminServerInfoForm.GetFormContentAsText function called from TMainForm.DoCurrentSectionChanged

The same exception appears when user chooses menu File->Copy Active Page As Text
Exception gets thrown from third party VCL component.

A workaround would be to suppress exception shown in TAdminServerInfoForm.GetFormContentAsText and return text which is collected at the moment exception occurs. Something like this:

try
<old body>
except
end;
Result:=S;
end;

Please wrap the function so we will get it workarounded in next version.
[8 Dec 2008 9:31] Mike Lischke
Since this problem is really hard to reproduce I took some steps to at least

1) Avoid any possible access violation due to non-initialized variables related to this problem.
2) Capture any exception in the relevant code and let the user know what happend, asking for opening a new bug report with the data shown in the message.

Hopefully this will avoid the problem mentioned here or at least help us to better track down what happens.

Thanks for your patience.