RESOLVED FIXED Bug 37720
HTMLFrameSetElement-window-eventListener-attributes.html sometimes crashes on SnowLeopard Release
https://bugs.webkit.org/show_bug.cgi?id=37720
Summary HTMLFrameSetElement-window-eventListener-attributes.html sometimes crashes on...
Adam Roben (:aroben)
Reported 2010-04-16 11:49:11 PDT
HTMLFrameSetElement-window-eventListener-attributes.html sometimes crashes on SnowLeopard Release. Unfortunately the bots don't seem to be saving crash logs. :-(
Attachments
test (will assert) (343 bytes, text/html)
2010-04-16 13:47 PDT, Alexey Proskuryakov
no flags
proposed fix (12.78 KB, patch)
2010-04-16 15:20 PDT, Alexey Proskuryakov
abarth: review+
Adam Roben (:aroben)
Comment 1 2010-04-16 11:52:55 PDT
I added this test to the Skipped file in r57731.
Alexey Proskuryakov
Comment 2 2010-04-16 12:22:53 PDT
Alexey Proskuryakov
Comment 3 2010-04-16 13:00:54 PDT
There is a good chance that the disabled test is innocent. In debug mode, fast/dom/Window/HTMLBodyElement-window-eventListener-attributes.html randomly crashes, which may make subsequent tests crash: run-webkit-tests --repeat-each 100 fast/dom/Window The debug crash is an assertion failure, ASSERT(m_wrapper || !m_jsFunction) in JSEventListener::jsFunction().
Alexey Proskuryakov
Comment 4 2010-04-16 13:47:57 PDT
Created attachment 53560 [details] test (will assert)
Adam Roben (:aroben)
Comment 5 2010-04-16 14:02:33 PDT
(In reply to comment #3) > There is a good chance that the disabled test is innocent. > > In debug mode, > fast/dom/Window/HTMLBodyElement-window-eventListener-attributes.html randomly > crashes, which may make subsequent tests crash: Should we skip this test instead? This has now crashed on Windows as well: http://build.webkit.org/results/Windows%20Debug%20(Tests)/r57731%20(12262)/results.html
Alexey Proskuryakov
Comment 6 2010-04-16 15:20:39 PDT
Created attachment 53570 [details] proposed fix
Adam Barth
Comment 7 2010-04-17 13:21:26 PDT
Comment on attachment 53570 [details] proposed fix Interesting bug. It seems like another solution is to keep the body wrapper alive. Can you and some text to the ChangeLog explaining why this approach is better? + window onject typo
Alexey Proskuryakov
Comment 8 2010-04-17 23:09:36 PDT
Committed <http://trac.webkit.org/changeset/57790>. > It seems like another solution is to keep the body wrapper alive. > Can you and some text to the ChangeLog explaining why this approach is better? Maybe it's better to explain it here - ChangeLog explains what was done in a patch, not what wasn't done. The reason I didn't fix this by keeping body wrapper alive was that it would be too subtle and roundabout. But thinking about it now, there is a bigger issue - the body element can be replaced via DOM manipulation, or even adopted by another document.
Alexey Proskuryakov
Comment 9 2010-04-17 23:12:38 PDT
Also, for posterity - I didn't figure out how the problem and the assertion failure resulted in release mode crashes. There is some chance that the random crashes were something different - if so, we'll hear from them again.
Note You need to log in before you can comment on or make changes to this bug.