Bug 26094

Summary:

Unreproducible crashes below JSC::Interpreter::execute

Product:

WebKit

Reporter:

John Moe <john>

Component:

New Bugs

Assignee:

Nobody <webkit-unassigned>

Status:

RESOLVED WORKSFORME

Severity:

Normal

CC:

barraclough, ggaren

Priority:

Version:

528+ (Nightly build)

Hardware:

Mac

OS:

OS X 10.5

Attachments:

Description	Flags
Crash r43436	none
crash r44111	none
Crash r44282	none

John Moe

Reported 2009-05-29 18:32:07 PDT

Not sure how to reproduce, but it has happened twice so I am attaching the stack traces.

Attachments
Crash r43436 (2.50 KB, text/plain) 2009-05-29 18:33 PDT, John Moe	no flags	Details
crash r44111 (2.50 KB, text/plain) 2009-05-29 18:33 PDT, John Moe	no flags	Details
Crash r44282 (2.67 KB, text/plain) 2009-06-07 17:18 PDT, John Moe	no flags	Details
View All Add attachment proposed patch, testcase, etc.

John Moe

Comment 1 2009-05-29 18:33:28 PDT

Created attachment 30799 [details] Crash r43436

John Moe

Comment 2 2009-05-29 18:33:51 PDT

Created attachment 30800 [details] crash r44111

John Moe

Comment 3 2009-06-07 15:25:05 PDT

And once more today. Am I the only person seeing this?

Gavin Barraclough

Comment 4 2009-06-07 16:24:27 PDT

We had a bug making crashes with this backtrace common pre r43885, which certainly addressed the majority of cases of this problem. The crash on r44111 is interesting since it is the first instance I've seen of a crash here since that fix went in. If you continue to see this crash repeat, then any steps to reproduce (any websites that might be candidates for triggering the crash, behavior – the last problem tended to manifest when you returned to your machine having left it unused for a while & under high memory load, etc) would be hugely appreciated. cheers, G.

John Moe

Comment 5 2009-06-07 17:18:16 PDT

Created attachment 31035 [details] Crash r44282 I believe I was on fark.com and had just pressed command-L. Not reproducible.

John Moe

Comment 6 2009-07-12 14:36:55 PDT

This has stopped happening to me. I got a new computer, a new Safari was released, and new WebKit versions were released. The world may never know the cause.

Note You need to log in before you can comment on or make changes to this bug.