Comments on: Another Acid 3 Fix: Ranges and Document Mutation

By: Maciej Stachowiak

Maciej Stachowiak — Mon, 17 Mar 2008 00:56:30 +0000

eAi: details of your hardware and network setup would be helpful, in a bug report. I would suggest filing a new one at http://bugs.webkit.org, it is not very complicated to file a bug and if it is a duplicate we can relate it.

By: Mark Rowe

Mark Rowe — Mon, 17 Mar 2008 00:50:41 +0000

@eAi: Please file a new bug report and include the information that you mentioned.

By: eAi

eAi — Sun, 16 Mar 2008 22:27:14 +0000

Oh, and I’m on Safari 3.0.4, WebKit r31084 on OS X 10.5.2.

By: eAi

eAi — Sun, 16 Mar 2008 22:24:56 +0000

darin, everyone seems to get results other than 91 occasionally. I used to get 88, 89 and 90 randomly before the most recent fix. I now almost always get 91, but just managed to get 89 on the latest build, with test 78 failing (expected 90 got 0 – getRotationOfChar(0) failed) and test 77 failing (expected 4776 but got 5550 – getComputedTextLength failed).

Is there already an open bug I can contribute anything to?

By: darin

darin — Sun, 16 Mar 2008 20:29:54 +0000

Folks, if you see results other than 91/100, please write a bug report. We need specifics, like what platform you’re running WebKit on.

Blog comments aren’t good places for bug reports — we don’t track them or anything.

By: Sebastian

Sebastian — Sun, 16 Mar 2008 15:03:08 +0000

The first time I tried, I got 86, now every time I get 87… I don’t know what’s going on there…

By: Z

Sun, 16 Mar 2008 13:37:42 +0000

Same as xfinite. Except that I got pretty unstable test results – varying from 88 to 91.

By: Matt Lilek

Matt Lilek — Sat, 15 Mar 2008 19:29:22 +0000

From what you’ve pasted, it looks like you’re hitting Bug 17860 .

Reproducible crashes should always be reported, whether they occur over multiple builds or not. Even if you’re not sure whether something is a bug or not, it’s better to report it and have someone with more insight to investigate it, than to not have it reported at all.

By: xfinite

xfinite — Sat, 15 Mar 2008 18:34:13 +0000

As other commenters pointed out in the previous post, current WK builds are rather flaky when running the Acid3 test.
Case in point, I downloaded today’s build (31055) and loaded the acid3 test site immediately. The first time it ran, it briefly paused at 64% and moved up to 89. I hit reload and it went straight up, to 88. Then after 5 seconds or so I hit reload again and it then stalled at 64% – it was waiting for something to load – and then WK crashed.

top of stackdump;
Thread 0 Crashed:
0 ??? 0000000000 0 + 0
1 com.apple.WebCore 0×00f46d61 WebCore::SubresourceLoader::didFinishLoading() + 49
2 com.apple.Foundation 0×9090d8b7 -[NSURLConnection(NSURLConnectionReallyInternal) sendDidFinishLoading] + 87
3 com.apple.Foundation 0×9090d844 _NSURLConnectionDidFinishLoading + 68

running on Mac OS X 10.5.2, MBP rev. 1.

About these types of crashes in WK, is it useful to file bug reports for crashes like these that may be gone the next build? I guess if a crash should be reproducible over a number of builds before it should be reported as a real bug? Sorry if all of this is obvious, my brain is out of phazon.