Bug #70632 | Workbench Error Code 2008: MySQL Client ran out of memory | ||
---|---|---|---|
Submitted: | 16 Oct 2013 9:00 | Modified: | 16 Oct 2013 11:30 |
Reporter: | Mark Rouse | Email Updates: | |
Status: | Duplicate | Impact on me: | |
Category: | MySQL Workbench | Severity: | S5 (Performance) |
Version: | 6.0.7.11215 | OS: | Windows (7 64-bit) |
Assigned to: | CPU Architecture: | Any |
[16 Oct 2013 9:00]
Mark Rouse
[16 Oct 2013 10:19]
Peter Laursen
You have probably reached the memory allocation limit of a 32 bit application. WB is not available as 64 bit (not for Windows at least). Also note that the situation as regards memory allocation for a 32 bit application is actually worse on 64 bit Windows than on 32 bit Windows. There are only few GUI clients that has an option for 64 bit. I am only aware of SQLyog, actually. Peter (not a MySQL/Oracler person)
[16 Oct 2013 10:24]
Peter Laursen
Besides you claim that your Windows is 64 bit. But the OS information returned by WB logs says 32 bit. Is it you or WB who is inconsistent? Maybe WB return 32 bit as it runs in the 32-bit subsystem ('syswow64')?
[16 Oct 2013 10:28]
Mark Rouse
My server is 64-bit as is the OS MySQL Server sits on on but Workbench is 32-bit and is installed on a separate PC from my server which is 32-bit.
[16 Oct 2013 10:33]
Mark Rouse
Is there anything else that I can do other than use another GUI?
[16 Oct 2013 10:39]
Peter Laursen
If the client is running on a 32 bit system, I doubt that another GUI will make much difference. But you may try a few others, of course. (Peter - and still not an official MySQL/Oracle person)
[16 Oct 2013 11:11]
Mark Rouse
Are there any plans to release a 64-bit version of Workbench?
[16 Oct 2013 11:30]
MySQL Verification Team
Thank you for the bug report. Duplicate with http://bugs.mysql.com/bug.php?id=65728 .