Bug 27178 – Safari hangs for a minute or two before continuing to load

• Component: Page Loading
• Status: UNCONFIRMED

[Simone Manganelli]

Created attachment 32615 [details]
60 second sample of WebKit when it hangs

Summary: Sometimes WebKit decides to hang for a significant period of time, around 2 or 3 minutes or so, before deciding to un-hang itself and continue loading.  Typically this happens just after clicking on a specific link, as WebKit tries to start loading a new page.  This problem can happen multiple times in a single session, too; after experiencing the problem, it can happen again in another few minutes.


Steps to Reproduce:

1.  Open WebKit.

2.  Do a bunch of web browsing for ~15 minutes or so.  Usually WebKit must have been open for a while before the bug is triggered.

3.  Click on a link that will open a new window.  (It doesn't seem to be any specific link that triggers the bug, but it *does* usually seem to be a link that opens a new window.)  Note that WebKit hangs for about 2-3 minutes before it decides to open the window and continue loading as normal.


Expected Results: I expect WebKit not to hang when I click on a link that opens a new window.


Actual Results: WebKit hangs for 2-3 minutes.


Regression: This has only happened in recent builds of WebKit, probably for the last month or so.  I don't remember this happening before with builds of WebKit used in the Safari 4 beta, but it has been happening with Safari 4 final.


Notes: I have no InputManagers installed.  I am using WebKit r45702.  I have also attached a sample of WebKit for 60 seconds when this problem happens.  This has also been filed in Apple's bug reporter: rdar://problem/7051097

[Mark Rowe (bdash)]

A website is doing a synchronous XHR.  That is an inherently synchronous operation.

[Simone Manganelli]

Sure, it's synchronous, but it shouldn't be blocking the app for 2-3 minutes; I should still be able to look at my other tabs and browse around.

There's some other change that's causing this problem though, because it's only recently that this has been happening.  And 2-3 minutes to do a synchronous XML request seems incredibly excessive.  What could possibly be taking that long to load?

[Mark Rowe (bdash)]

(In reply to comment #2)
> Sure, it's synchronous, but it shouldn't be blocking the app for 2-3 minutes; I
> should still be able to look at my other tabs and browse around.

That's true.

> There's some other change that's causing this problem though, because it's only
> recently that this has been happening.  And 2-3 minutes to do a synchronous XML
> request seems incredibly excessive.  What could possibly be taking that long to
> load?

Without information about what is being loaded all I could do is speculate.