Bug #52384 | Performing query produced mysql workbench crash | ||
---|---|---|---|
Submitted: | 26 Mar 2010 7:56 | Modified: | 1 May 2010 6:52 |
Reporter: | Mike Emmott | Email Updates: | |
Status: | No Feedback | Impact on me: | |
Category: | MySQL Workbench: SQL Editor | Severity: | S3 (Non-critical) |
Version: | 5.2.16beta | OS: | Windows (xp sp3) |
Assigned to: | CPU Architecture: | Any |
[26 Mar 2010 7:56]
Mike Emmott
[26 Mar 2010 11:59]
Susanne Ebrecht
Many thanks for writing a bug report. I am not able to follow you ... What do you thing is the bug here?
[29 Mar 2010 16:40]
Mike Emmott
The 'what went wrong': A message box came up, telling me that the workbench had caught an internal error, and with a button to press to copy details into Windows' clipboard. The message box invited me to file a bug report. So I clicked the 'copy the details' button and filed this bug report. The trigger for this happening seemed to be asking the workbench to execute the query as given in my initial report. Now, I'm not an experienced SQL author and I doubt that my SQL is good. I'm afraid I didn't notice any more detail from the message box than this. Sorry if there is a key phrase you would like to see which hasn't copied over with the 'copy the details' button's output.
[30 Mar 2010 7:23]
Mike Emmott
I have two guesses as to what the bug might be: 1) it fell over trying to parse bad sql 2) taking the tool into and out of Windows 'Standby' leaves it undermined in some way 3) taking it and the mysql db into and out of Windows 'Standby' somehow makes its connection go stale, but it doesn't notice and doesn't error trap it. Three guesses for the price of two. There's an offer you can't refuse .. :)
[1 Apr 2010 6:52]
Susanne Ebrecht
Many thanks for writing a bug report. Unfortunately, we have too less informations here for making a deeper analysis. We either need to know exactly how we can reproduce this or we need the backtrace. Please read: http://bugs.mysql.com/how-to-report.php
[1 May 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".