Closed
Bug 702432
Opened 14 years ago
Closed 12 years ago
loading missing page on support.microsoft.com leaves previous page active while showing url of missing page
Categories
(Core :: Networking, defect)
Tracking
()
RESOLVED
INCOMPLETE
People
(Reporter: karlt, Unassigned)
References
()
Details
(Keywords: memory-leak)
Attachments
(2 files)
27.08 KB,
text/plain
|
Details | |
1.20 KB,
patch
|
Details | Diff | Splinter Review |
STR:
1) Load any page. about:home will do.
2) clear the url from the location bar.
3) Enter http://support.microsoft.com/support/kb/articles/Q136/2/04.asp and press return.
Actual results:
Previous page remains active while the location bar tells me I'm on
http://support.microsoft.com/support/kb/articles/Q136/2/04.asp
Expected results:
Some indication of what went wrong.
Problem exists on m-c and Firefox 7.
wget is served a 404 for this url, but this problem does not happen with 404s from other servers.
Reporter | ||
Updated•14 years ago
|
Summary: loading missing page on support.microsoft.com leaves previous page active while showing url of mssing page → loading missing page on support.microsoft.com leaves previous page active while showing url of missing page
Reporter | ||
Comment 1•14 years ago
|
||
This seems to be associated to a RDF service leak at the end of the browser session and subsequent sessions (that don't actually load this url).
Comment 2•14 years ago
|
||
I can reproduce on Firefox 7, but not on m-c nightly.
Reporter | ||
Comment 3•14 years ago
|
||
Reporter | ||
Comment 4•14 years ago
|
||
nsDocumentOpenInfo::DispatchContent() returns NS_ERROR_FILE_NOT_FOUND for the
content of type "application/x-asp".
nsDocumentOpenInfo::OnStartRequest() returns the error code
through nsUnknownDecoder::FireListenerNotifications()
to nsUnknownDecoder::OnStopRequest(),
which passes the error to nsDocumentOpenInfo::OnStopRequest(),
which does nothing because m_targetStreamListener is NULL and returns NS_OK.
nsUnknownDecoder::OnStopRequest then returns the NS_OK from
nsDocumentOpenInfo::OnStopRequest(), and the failure status is lost forever.
Is the request meant to be cancelled at some stage?
Component: Document Navigation → Networking
QA Contact: docshell → networking
Reporter | ||
Comment 5•14 years ago
|
||
This fixes the symptoms in comment 0, but the error message that I get is a "File not found" error message.
"Firefox can't find the file at http://support.microsoft.com/support/kb/articles/Q136/2/04.asp" doesn't seem quite right.
![]() |
||
Comment 6•14 years ago
|
||
Canceling the request doesn't make all that much sense in some ways from there because the request is all done: it's sending OnStopRequest.
But yes, that might be the simplest fix for this issue.....
Karl, did you mean to request review?
Reporter | ||
Comment 7•14 years ago
|
||
I didn't consider this ready for review, thanks. I meant to go back and investigate further, but haven't got to it. I suspect we should be presenting a 404 message, but didn't really work out what was happening.
Reporter | ||
Comment 8•12 years ago
|
||
The server is responding differently now.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → INCOMPLETE
You need to log in
before you can comment on or make changes to this bug.
Description
•