Bug 7084

Summary:

REGRESSION: Multiple load events dispatched to <body> (makes layout tests hang)

Product:

WebKit

Reporter:

mitz

Component:

New Bugs

Assignee:

Maciej Stachowiak <mjs>

Status:

VERIFIED FIXED

Severity:

Blocker

CC:

darin, matt, mjs

Priority:

Keywords:

HasReduction, Regression

Version:

420+

Hardware:

Mac

OS:

OS X 10.4

URL:

http://www.haaretz.co.il/?from=hasot

Attachments:

Description	Flags
Testcase	none

mitz

Reported 2006-02-05 06:55:13 PST

Safari is unresponsive and its CPU usage is very high when going to the above URL.

Attachments
Testcase (120 bytes, text/html) 2006-02-05 07:25 PST, mitz	no flags	Details
View All Add attachment proposed patch, testcase, etc.

Alexey Proskuryakov

Comment 1 2006-02-05 07:06:38 PST

That would be very new - I don't see this problem with r12570. Possibly a regression from a fix in bug 7079 - it's known to hang on at least one regression test.

mitz

Comment 2 2006-02-05 07:14:56 PST

(In reply to comment #1) > That would be very new - I don't see this problem with r12570. Possibly a > regression from a fix in bug 7079 - it's known to hang on at least one > regression test. > This could very well be it: it looks like the root cause for this bug is that <body>'s onload handler is being called multiple times.

mitz

Comment 3 2006-02-05 07:25:28 PST

Created attachment 6273 [details] Testcase This demonstrates that the onload handler is being called twice.

Darin Adler

Comment 4 2006-02-05 09:21:57 PST

Maciej was looking at this last night -- it's from his last check-in with "event clean-up". We'll probably need to roll that out.

Darin Adler

Comment 5 2006-02-05 09:25:17 PST

Alexey believes Maciej had a fix ready when he went to sleep last night.

Darin Adler

Comment 6 2006-02-05 10:59:09 PST

Rolling out the change because it's preventing us from running layout tests. Maciej will re-land it soon.

Joost de Valk (AlthA)

Comment 7 2006-02-06 11:22:46 PST

*** Bug 7100 has been marked as a duplicate of this bug. ***

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