Bug #53273 SIGBUS exception

• Submitted: 28 Apr 2010 23:07
• Modified: 26 May 2010 4:38
• Reporter: Matthew Hall
• Status: Can't repeat
• Category: MySQL Workbench: SQL Editor
• Severity: S1 (Critical)
• Version: 5.2.21
• OS: MacOS (10.6.3)
• CPU Architecture: Any

[28 Apr 2010 23:07] Matthew Hall

Description:
MySQL Workbench consistently crashes with a SIGBUS exception after a few minutes of 'Altering'  SQL routines

How to repeat:
Left click on a routine, select 'Alter Routine...', and start editing. A crash will follow after a few minutes of editing.

Stack trace attached.

[28 Apr 2010 23:09] Matthew Hall

stack trace

Attachment: stack trace (application/octet-stream, text), 49.07 KiB.

[29 Apr 2010 4:01] Valeriy Kravchuk

What exact edits you made? Copy-pasting some SQL, typing, something else? How big is your routine's text?

[29 Apr 2010 17:56] Matthew Hall

Attached is a copy of the routine I was editing just now with the associated stack trace.

I was typing text, then paused for a few seconds, and the crash occurred when I was doing nothing.

[29 Apr 2010 17:57] Matthew Hall

SQL being edited before crash

Attachment: crash.sql (application/octet-stream, text), 2.01 KiB.

[29 Apr 2010 17:59] Matthew Hall

Stack trace associated with SQL file being edited

Attachment: stack trace2 (application/octet-stream, text), 52.97 KiB.

[12 May 2010 16:13] Valeriy Kravchuk

Please, check with a newer version, 5.2.21, and inform about the results.

[12 May 2010 23:59] Matthew Hall

Been using 5.2.21 all day with no problems. Looks like it's fixed.

[14 May 2010 17:50] Valeriy Kravchuk

Looks like this is not repeatable with 5.2.21 any more.

[24 May 2010 22:43] Matthew Hall

Although much less frequent than in 5.2.20, the SIGBUS exceptions are still there in 5.2.21. I have seen three so far today. They seem to occur at random, with no specific action triggering them. Last stack trace attached.

[24 May 2010 22:44] Matthew Hall

SIGBUD stack trace

Attachment: stack trace 3 (application/octet-stream, text), 54.31 KiB.

[26 May 2010 4:38] Matthew Hall

Pasting this query into the SQL Query tab will reliably produce a SIGBUS exception:

select url, width, sum(num_impression) as imp, sum(num_click) as click, sum(num_impression)/sum(num_click) as ctr,sum(num_impression*paid_cpm/1000)/sum(num_click) as cpc,
sum(num_impression*paid_cpm)/sum(num_impression) as paidcpm, sum(num_impression*bid_cpm)/sum(num_impression) as bidcpm, sum(num_impression*paid_cpm/1000) as cost, 
sum(num_impression)/sum(num_bid_request) as win_rate ,
sum(num_bid_request)/sum(num_request) as match_rate, sum(num_bid_request) bid_request, sum(num_request) as request
from adwiser.performance_flat where log_date>'2010-04-01' and url like '%wrong%' group by url,width order by request desc

[26 May 2010 4:39] Matthew Hall

Stack trace

Attachment: stack trace 5 (application/octet-stream, text), 44.31 KiB.