Bug #60238 workbench crashes when changing path to mysqldump
Submitted: 24 Feb 2011 15:56 Modified: 25 Feb 2011 17:34
Reporter: Ciprian Dobre-Trifan Email Updates:
Status: Duplicate Impact on me:
None 
Category:MySQL Workbench: Administration Severity:S3 (Non-critical)
Version:5.2.31a CE OS:Windows (XP SP3 32bit)
Assigned to: CPU Architecture:Any

[24 Feb 2011 15:56] Ciprian Dobre-Trifan
Description:
workbench crashes when changing path to mysqldump from Edit -> preferences -> administrator. Crash happens after pressing Ok.

How to repeat:
change path to mysqldump (i chose the one in the Mysql Server 5.5 / bin directory)
[24 Feb 2011 16:40] MySQL Verification Team
Which version are you using? I couldn't repeat with 5.2.31.
[25 Feb 2011 7:35] Ciprian Dobre-Trifan
I have versino 5.2.31 revision 7115

I also noticed in the meanwhile that i get this in the output window whenever i open Admin (i press Manage import/export in main page) :

ctrl_be: Query Error Error executing 'MySQL server has gone away'
SHOW GLOBAL STATUS.
SQL Error: 2006
WMIShell: Set filters for local windows cli
Traceback (most recent call last):
  File "C:\Program Files\MySQL\MySQL Workbench 5.2 CE\modules\wb_admin_grt.py", line 305, in openExportImport
    tab.wait_server_check(4)
  File "C:\Program Files\MySQL\MySQL Workbench 5.2 CE\modules\wb_admin_grt.py", line 133, in wait_server_check
    while self.configuration.last_is_running_check is None and time.time() - t < timeout:
  File "C:\Program Files\MySQL\MySQL Workbench 5.2 CE\mforms.py", line 665, in <lambda>
    __getattr__ = lambda self, name: _swig_getattr(self, Box, name)
  File "C:\Program Files\MySQL\MySQL Workbench 5.2 CE\mforms.py", line 34, in _swig_getattr
    raise AttributeError,name
AttributeError: last_is_running_check

Do you need a specific version of python installed ? I have Py 3.1.3 installed on my machine.
[25 Feb 2011 8:18] Valeriy Kravchuk
I also can not repeat this on 32-bit XP SP3. I do not have any separate Python installation, so the one from Workbench bin subdirectory (2.6.3) is used.

Can you try to uninstall your newer Python version (or change PATH/PYTHONPATH/whatever to prevent its execution) and check if this will change anything?
[25 Feb 2011 9:05] Ciprian Dobre-Trifan
I uninstalled python. I moved the path entry for MySQL Server 5.5/bin before the MySQL Server 5.1 (i have this one installed as well) but with no effect.

I am also on WinXP SP3 32bit
[25 Feb 2011 12:01] Ciprian Dobre-Trifan
I do not get any problems when using the workbench on the 5.1 server.

I uninstalled the 5.1 to avoid possible conflict of python versions, but the issue persists.

I've noticed though that the workbench no longer crashes after changing the path to mysqldump if I am not in the Admin workbench (so by editing the path from the main window, without the Admin window open it's ok).

Still, when trying to perform an actual dump I get a full crash of the workbench (Windows pops up a "mysqldump.exe Application Error" window saying "The instructions at '0x....' referenced memory at '0x00000000'. The memory could not be read." Sounds to me like a null pointer exception.
[25 Feb 2011 12:06] Ciprian Dobre-Trifan
This is what's in the output following the crash during the dump (except for the weird python errors in the initial message described previously):

13:53:09 Dumping licentarb (departament, curriculum, my_temp_table_copy, angajat, my_temp_table)
Running: "C:\Program Files\MySQL\MySQL Server 5.5\bin\mysqldump.exe" --defaults-extra-file="d:\docume~1\cgdobre\locals~1\temp\tmpiat9dx"  --no-create-info=FALSE --order-by-primary=FALSE --force=FALSE --no-data=FALSE --tz-utc=TRUE --flush-privileges=FALSE --compress=FALSE --replace=FALSE --host=127.0.0.1 --insert-ignore=FALSE --extended-insert=TRUE --user=root --quote-names=TRUE --hex-blob=FALSE --complete-insert=FALSE --add-locks=TRUE --port=3307 --disable-keys=TRUE --delayed-insert=FALSE --create-options=TRUE --delete-master-logs=FALSE --comments=TRUE --default-character-set=utf8 --max_allowed_packet=1G --flush-logs=FALSE --dump-date=TRUE --lock-tables=TRUE --allow-keywords=FALSE --events=FALSE "licentarb" "departament" "curriculum" "my_temp_table_copy" "angajat" "my_temp_table"
Operation failed with exitcode -1073741819
[25 Feb 2011 12:24] Ciprian Dobre-Trifan
I did not mention but perhaps it's relevant. I had also the Gui Tools (r16 i think) and after the 5.2 OSS version (don't remember exactly which subversion or revision) of the workbench before going to the current workbench version.

I only have this last one installed at this moment though.
[25 Feb 2011 17:34] Valeriy Kravchuk
If this crash happens with mysqldump from 5.5.x, this is a duplicate of Bug #59234 actually.