Bug #69447 Critical error after execute query (all queries)
Submitted: 12 Jun 2013 1:04 Modified: 12 Jul 2013 11:59
Reporter: Junior Conte juniorconte Email Updates:
Status: No Feedback Impact on me:
None 
Category:MySQL Workbench Severity:S3 (Non-critical)
Version:5.2.47 OS:MacOS
Assigned to: CPU Architecture:Any
Tags: query crash

[12 Jun 2013 1:04] Junior Conte juniorconte 
Description:
Process:         MySQLWorkbench [6715]
Path:            /Applications/MySQLWorkbench.app/Contents/MacOS/MySQLWorkbench
Identifier:      com.oracle.mysql.workbench
Version:         5.2.47 (1)
Code Type:       X86 (Native)
Parent Process:  launchd [233]

Date/Time:       2013-06-11 21:40:54.374 -0300
OS Version:      Mac OS X 10.7.5 (11G63)
Report Version:  9

Interval Since Last Report:          259056 sec
Crashes Since Last Report:           3
Per-App Interval Since Last Report:  1159 sec
Per-App Crashes Since Last Report:   3
Anonymous UUID:                      D5929B04-4EB8-46CF-AA4B-35BF03C01E75

Crashed Thread:  0  Dispatch queue: com.apple.main-thread

Exception Type:  EXC_BAD_ACCESS (SIGBUS)
Exception Codes: KERN_PROTECTION_FAILURE at 0x00000000fefff000

---

If necessary, i send complete stack error.

How to repeat:
1- Click table with right button
2- Click into submenu (Select Rows - Limit 1000)
3- The system show spinner before the error

The error does not occur in version 2.5.46
[12 Jun 2013 11:59] MySQL Verification Team 
Thank you for the bug report. Please elaborate your environment: The exception happens all the time? Local/Remote connection? Which kind of connection? etc.
I couldn't repeat with below hardware and local connection:

MySQL Workbench CE for Mac OS X version 5.2.47  revision 10398
Configuration Directory: /Users/miguel/Library/Application Support/MySQL/Workbench
Data Directory: /Applications/MySQLWorkbench.app/Contents/Resources
Cairo Version: 1.9.1
OS: Darwin 12.4.0
CPU: 4x Intel(R) Core(TM) i5-3210M CPU @ 2.50GHz, 16.0 GB RAM
[13 Jul 2013 1: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".