- Windows XP SP2
- Apple Safari for Windows 3.1.1 or 3.1.2 using a WebKit nightly build for Windows from http://nightly.webkit.org/
- Intel P4 2.4 GHz CPU (single core)
How often it happens: always
1. using any nightly WebKit build from nightly.webkit.org after build r34388 (the first one avaliable on that website is r34577)
2. go to http://acid3.acidtests.org/ to take the Acid3 test
3. the web browser hangs, the test shows:
The browser no longer responds to any commands, it doesn't update its window anymore (if I open another application that covers the browser window, and then minimize this application, the browser window shows parts of the application window that I minimized) and needs to be closed via task manager. It does not crash, it simply hangs and doesn't respond to anything. Looks like an infinite loop or deadlock threading issue ?
The last WebKit nightly build for Windows on nightly.webkit.org that doesn't hang is r34388.
The next WebKit nightly build for Windows on nightly.webkit.org is r34577, and it hangs. Every WebKit nightly build after that hangs too.
So, the change that caused the hang must have happened somewhere in between builds r34388 and r34577 (for Windows).
I am getting the same behavior on a web application I am working on (sorry, not on a production server I can share with you).
When I reach a page with a pretty big JS file (complex behavior, developed over GWT) the CPU spikes at 100%, and the browser hangs unresponsive.
I can't point out when it started since this is the first build I've checked out for some time due to a different bug, but it reproduces for me on build r35130 for Windows.
WebKit Nightly build r35354 for Windows no longer has this behavior, so the bug can be considered fixed.
Same for me, resolved for build r35354 on Windows.