Bug 50753

Summary: crash during page refresh in r73490
Product: WebKit Reporter: Jyrki Wahlstedt <jyrki.wahlstedt>
Component: WebKit Misc.Assignee: Nobody <webkit-unassigned>
Status: RESOLVED DUPLICATE    
Severity: Normal CC: ap, aroben
Priority: P2    
Version: 528+ (Nightly build)   
Hardware: PC   
OS: Windows XP   
Attachments:
Description Flags
crash dump from r73490 none

Jyrki Wahlstedt
Reported 2010-12-09 05:23:19 PST
Created attachment 76049 [details] crash dump from r73490 Not related to the page, maybe... Dump attached
Attachments
crash dump from r73490 (107.31 KB, application/octet-stream)
2010-12-09 05:23 PST, Jyrki Wahlstedt 		no flags
Details
View All Add attachment proposed patch, testcase, etc.
Alexey Proskuryakov
Comment 1 2010-12-09 10:47:34 PST
Can you tell us what site you've been refreshing? Can you reproduce this? For Apple engineers: see <rdar://problem/6474002>.
Jyrki Wahlstedt
Comment 2 2010-12-10 00:02:14 PST
(In reply to comment #1) > Can you tell us what site you've been refreshing? Can you reproduce this? > > For Apple engineers: see <rdar://problem/6474002>. IIRC, the site (and page) was http://ilmatieteenlaitos.fi/saa/Helsinki, and this was a one-timer.
Jyrki Wahlstedt
Comment 3 2010-12-10 04:01:53 PST
Not sure, if this helps, or should I make this another bug, but I have managed to get the build system working on my laptop, now at r73689, and when I was refreshing my Twitter homepage, that stuck at almost the end, and when I attached VC 2005 Express to it and gave the command "Break all", it always showed the same line, 3761 in file fastmalloc.cpp belonging to JavaScriptCore.dll...
Alexey Proskuryakov
Comment 4 2010-12-10 08:53:26 PST
This is almost certainly a different bug. I probably wouldn't file it unless it were reproducible. The crash here is inside CoreGraphics.
Jyrki Wahlstedt
Comment 5 2011-02-15 02:39:17 PST
hasn't happened since, hence by me can be closed!
Adam Roben (:aroben)
Comment 6 2011-02-15 05:39:47 PST
This and bug 49715 are about the same crash. I'm glad to hear it isn't affecting you anymore. *** This bug has been marked as a duplicate of bug 49715 ***
Note You need to log in before you can comment on or make changes to this bug.