Summary: | [crash] Trying to load a test page in a new tab | ||||||||
---|---|---|---|---|---|---|---|---|---|
Product: | WebKit | Reporter: | Gérard Talbot <browserbugs2> | ||||||
Component: | DOM | Assignee: | Nobody <webkit-unassigned> | ||||||
Status: | RESOLVED INVALID | ||||||||
Severity: | Major | CC: | allen.sam, aroben, mrowe | ||||||
Priority: | P1 | Keywords: | HasReduction, InRadar, PlatformOnly | ||||||
Version: | 523.x (Safari 3) | ||||||||
Hardware: | PC | ||||||||
OS: | Windows XP | ||||||||
URL: | http://www.quirksmode.org/dom/w3c_css.html#t01 | ||||||||
Attachments: |
|
Description
Gérard Talbot
2007-06-23 13:12:08 PDT
Confirmed on Windows XP with Safari 3.0.2 Beta and r23677. Crash still happening in Safari 3.0.3 build 522.15.5 with the same steps to reproduce. Gérard and/or Matt, can you attach crash information to this bug as described at <http://webkit.org/quality/crashlogs.html>? Adam, I followed the instructions given in crashlogs.html. Now, I can attach the user.dmp file in here. I don't know/am not sure about the correct portion of the drwtsn32.log... Created attachment 15840 [details]
user.dmp of the crash
user.dmp file: I was not sure about the content-type: I chose plain text (text/plain).
Created attachment 15841 [details] Portion of DrWatson's crash log for bug 14340 Ok. Portion of crash data collected by DrWatson. I hope this is correct and sufficient. If there is a problem, let me know... One more detail. Before trying the steps to reproduce, I cleared Safari's cache. Good catch, Mitz! Yes, bug 14919 and this bug 14340 are the same since both have an <body onload="alert(...something...);"> execution to do. I am able to reproduce the crash with a minimized testcase (5 lines long). 5 lines long testcase: http://www.gtalbot.org/BugzillaSection/Bug14340-1.html *** Bug 14919 has been marked as a duplicate of this bug. *** Thanks for the bug report, crash log, and reduction, Gérard! They were very helpful in tracking this problem down. It turns out this is a Safari bug, not a WebKit bug, so we will continue to track this issue with <rdar://problem/5401061>. |