Bug #53861 random crash during stored procedure writing
Submitted: 20 May 2010 16:35 Modified: 10 Sep 2010 9:16
Reporter: Alex Rosario Email Updates:
Status: No Feedback Impact on me:
None 
Category:MySQL Workbench: SQL Editor Severity:S2 (Serious)
Version:5.2.25 GA (r6303) OS:MacOS (10.6.4)
Assigned to: CPU Architecture:Any
Tags: editor, stored procedure

[20 May 2010 16:35] Alex Rosario 
Description:
while attempting to create or edit a stored procedure, workbench beachballs then closes followed by the mac os x "the application unexpectedly quit" dialog. it used to happen a lot more often in previous beta releases, but i worked around it by writing the function in a text editor and copy-pasting it into the window; speed seems to be a factor here as well.

How to repeat:
this happens either when creating a stored procedure from scratch using the "add routine" functionality of a schema's query editor tab or editing an existing stored procedure by right-clicking a routine and choosing "alter routine." it's more likely to happen if a "create/edit stored procedure" window hasn't yet been created; chances of a crash also increase if you had added or edited a table beforehand during that app session. it's also more likely to happen the longer you take to complete adding/editing the procedure in this window (it's beachballed on me while typing many times).
[21 May 2010 9:08] Susanne Ebrecht 
Please provide core dump.
[21 Jun 2010 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".
[20 Jul 2010 20:33] Alex Rosario 
it's happening again; core dump attached this time.

i'm thinking it's something snow leopard related, since the build is primarily designated as leopard instead.
[10 Aug 2010 9:16] Susanne Ebrecht 
Please make sure that python 2.6.5 is installed.

Also we just published Workbench 5.2.26. Maybe you could give it a try.
[10 Sep 2010 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".