Bug 27392 - Loading of certain resources can hang when a website uses long running XMLHttpRequests and iframes
Summary: Loading of certain resources can hang when a website uses long running XMLHtt...
Status: UNCONFIRMED
Alias: None
Product: WebKit
Classification: Unclassified
Component: Frames (show other bugs)
Version: 528+ (Nightly build)
Hardware: Mac (Intel) OS X 10.5
: P2 Critical
Assignee: Nobody
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-07-17 15:26 PDT by Mario
Modified: 2014-03-07 11:33 PST (History)
3 users (show)

See Also:


Attachments
crashlog from latest nightly build 46042 (35.55 KB, application/octet-stream)
2009-07-18 02:51 PDT, Mario
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Mario 2009-07-17 15:26:20 PDT
I implemented a website for one of my customers that uses

a) ASP.NET AJAX 3.5
b) long running XMLHttpRequests initiated using ASP.NET AJAX functionality (approx. 30 seconds between request start and response)
c) an iframe

When the page in the iframe is reloaded due to form postbacks initiated by user interaction during the aforementioned XMLHttpRequest still waits for a server response, Safari 4.0.2 / WebKit (nightl build from July  17th) hangs and sometimes finally crashes. I can observe this behaviour with Safari 4.0.2 on an Intel Mac and a PC. On the PC I confirmed that the page in the iframe continues to load normally when the XMLHttpRequest gets a reponse from the server so that the XMLHttpRequest ends.

The same website can be viewed without problems e.g. in Firefox 2 / 3 / 3.1 / 3.5 / 3.5.1 and IE 7 / IE 8 and Opera 9 / 10. Alas, as the website is used internally at this time, I cannot provide a test link and therefore I hope this issue can be reproduced without a test link.
Comment 1 Brady Eidson 2009-07-17 16:00:49 PDT
First off, why if the title says "crashes", please provide a crash report - We can't explore a crash without a crash report.

Secondly, please try this again with the newest nightly.  We've recently made fixes in loading code that seem relevant here, if not the exact same issue.

Third, if the issue does still reproduce, it *will* be very difficult to explore it without a live example.  Note that a custom crafted reduced test case qualifies...
Comment 2 Mario 2009-07-18 02:51:09 PDT
Created attachment 33021 [details]
crashlog from latest nightly build 46042
Comment 3 Mario 2009-07-18 02:58:24 PDT
I just tried the latest bightly build again and it behaves a lot better than the current official Safari 4.0.2. Where Safari already hangs after the first or second click in the iframe (so that the page gets posted back), the nightly WebKit build behaved more stable.

But still (it seems especially when initiating a new postback in the iframe before the last response in the iframe is completely loaded so that the progress bar in the address bar disappeared), the nightly WebKit hangs sometimes and finally crashed. The crash log is attached.

I'll try to provide a reduced test case but this may take some days.
Comment 4 Mario 2009-07-27 09:02:29 PDT
A testcase is now available at http://xdf.c4b.de/devtest/serverpush.pages/lazytest.aspx.

One can see the following: as soon as the XMLHTTPRequest is running and waits for a response, some images do not load completely when one clicks the "Refresh" button. Instead, loading hangs and does not continue until the XMLHTTPRequest gets a server response (e.g. a "KeepAlive" after 30 seconds approx. -> displayed in the debug console that appears when one clicks on the bug in the lower left corner).

Alas, this testcase does not reproduce the crash in my case, so it seems there must apply some other conditions in my website to cause the crash. But at least, you should now be able to reproduce the hangs and possibly find a bugfix for this issue.
Comment 5 Brady Eidson 2009-07-27 09:12:56 PDT
Re-titling to reflect the only symptom that can be reproduced.