Closed Bug 1195037 Opened 10 years ago Closed 10 years ago

XMLHttpRequest causes high CPU use and incorrect shutdown after timeout

Categories

(Core :: Networking: HTTP, defect)

43 Branch
defect
Not set
normal

Tracking

()

RESOLVED DUPLICATE of bug 1199957

People

(Reporter: aleth, Unassigned)

Details

In Thunderbird, an XMLHttpRequest from chrome code of the form let request = new XMLHttpRequest(); request.open("GET", url); request.onload = function () {...}; request.onerror = () => {...}; request.ontimeout = () => {...}; request.onloadend = function() {...}; request.timeout = 15000; request.send(null); correctly calls ontimeout() followed by onloadend() when it timeouts. However, it seems something sticks around, as I see CPU usage going up to around 100%, and when the app is quit, it does not shut down correctly. Instead it hangs until force-quit (OS X). Any ideas as to what is going on here?
Version: 41 Branch → 43 Branch
PS. I don't think the test content/base/test/test_XHR_timeout.html can capture this behaviour, as the server faked by content/base/test/file_XHR_timeout.sjs will always close on its own after 3s.
(In reply to aleth [:aleth] from comment #1) > PS. I don't think the test content/base/test/test_XHR_timeout.html can > capture this behaviour, as the server faked by > content/base/test/file_XHR_timeout.sjs will always close on its own after 3s. (now lives in dom/base/test of course)
This appears to have been due to the patch landed in Bug 1170646, which has now been backed out.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.