Closed Bug 251213 Opened 21 years ago Closed 21 years ago

ftp urls fail to load

Categories

(Core :: Networking, defect, P1)

x86
All
defect

Tracking

()

RESOLVED FIXED
mozilla1.8alpha2

People

(Reporter: asa, Assigned: darin.moz)

References

()

Details

(Keywords: smoketest)

Attachments

(2 files)

In Windows build 20040712, FTP URLs fail to load. Steps to reproduce: 1. Load ftp://ftp.mozilla.org (or any other ftp url) Results: No page is loaded. You're left at the page you had previously loaded. No errors or allerts. Expected: Load the ftp url and display ftp listing
Summary: ftp urls fail to load → ftp urls fail to load
Whiteboard: http://test.mozilla.org/testrunner/test.cgi?run_id=212#67
2004071214 winxp... works here...
Christian, did you try with a new profile? I can't reproduce with my old (1.4 created) profile but I can reproduce with any new profiles I create. I also tested with 2004071214 on XP.
Installer build.
WFM win2k mozilla-win32-installer.exe 20040713 trunk w/ existing profile and w/ new profile i tested ftp://ftp.mozilla.org
Is anyone else able to reproduce this bug? Asa, is it possible that one of the ftp.mozilla.org mirrors was down when you tested? marking WORKSFORME if you can still reproduce this then please generate a FTP log file by setting the following environment variables: NSPR_LOG_MODULES=nsFTPProtocol:5,nsSocketTransport:5 NSPR_LOG_FILE=c:\log.txt then launch mozilla, reproduce the bug, and attach log.txt to this bug report. thanks!
Status: NEW → RESOLVED
Closed: 21 years ago
Resolution: --- → WORKSFORME
Whiteboard: http://test.mozilla.org/testrunner/test.cgi?run_id=212#67
Attached file log for ftp failure
Launch mozilla, create new profile, browser loads start page, ftp.mozilla.org entered into urlbar, failure, ftp.redhat.com entered into urlbar, failure.
I can reproduce this with any FTP urls I try to load. I can reproduce on a fresh clean install and an over the top of a previos release install. I've tested with several brand new profiles and can reproduce in all circumstances.
Status: RESOLVED → REOPENED
Resolution: WORKSFORME → ---
ok, seeing it on linux as well. debug build shows: ###!!! ASSERTION: Error: OnStartRequest() must be called before OnDataAvailable(): '(eOnStart == mParserContext->mStreamListenerState || eOnDataAvail == mParserContext->mStreamListenerState)', file /home/chb/mozilla/parser/htmlparser/src/nsParser.cpp, line 2389 Break: at file /home/chb/mozilla/parser/htmlparser/src/nsParser.cpp, line 2389 ###!!! ASSERTION: How'd we get here with an unknown type?: '!aParserContext.mMimeType.IsEmpty()', file /home/chb/mozilla/parser/htmlparser/src/CNavDTD.cpp, line 311 Break: at file /home/chb/mozilla/parser/htmlparser/src/CNavDTD.cpp, line 311 ###!!! ASSERTION: How'd we get here with an unknown type?: '!aParserContext.mMimeType.IsEmpty()', file /home/chb/mozilla/parser/htmlparser/src/nsExpatDriver.cpp, line 985 Break: at file /home/chb/mozilla/parser/htmlparser/src/nsExpatDriver.cpp, line 985 WARNING: NS_ENSURE_TRUE(mSink) failed, file /home/chb/mozilla/parser/htmlparser/src/nsExpatDriver.cpp, line 1005 Error loading URL ftp://ftp.redhat.com/ : 8000ffff (NS_ERROR_UNEXPECTED)
OS: Windows XP → All
whoa... that's wierd. i was just able to reproduce it too! moments ago it worked fine :-/ investigating....
OS: All → Windows XP
Asa: have you narrowed down the regression window at all? Did this just start appearing with today's builds? There weren't any changes to necko in the last week that could even remotely explain this (bonsai query: http://tinyurl.com/4mxgm).
303 rv = mBundle->FormatStringFromName(NS_LITERAL_STRING("DirTitle").get(), that fails, with NS_ERROR_UNEXPECTED (0x8000ffff), as seen in asa's log 307 if (NS_FAILED(rv)) return rv; this returns that code from onstartr, which cancels the channel this is all inside nsIndexedToHTML.cpp
i can repro w/ 20040712 and 20040713 seamonkey trunk on linux. trying other builds now.
i can repro the bug in 20040709 but not in 20040704 .. so that narrows the regression window. trying other builds now...
(In reply to comment #14) > i can repro the bug in 20040709 but not in 20040704 .. so that narrows the > regression window. trying other builds now... i take that back... the 20040704 build does not work either. i made the mistake of running mozilla 1.7 before testing the 20040704 build, and for some reason... that changed the results.
OS: Windows XP → All
Mozilla.org Linux 2004070706 WFM.
OS: All → Windows XP
bug definitely does not appear in the 20040621 trunk linux build. felix: is that with a fresh profile?
OS -> All
OS: Windows XP → All
OK, this regression started with the 6/29 trunk builds. I cannot reproduce the problem using the 6/28 trunk build.
This is a regression from bug 248847, which removed unused resource files. I must not have done something right when removing those files. Investigating....
> This is a regression from bug 248847, which removed unused resource files. I > must not have done something right when removing those files. Investigating.... This is _likely_ a regression from that bug. I haven't confirmed it yet. The problem seems to be related to the fact that the chrome.rdf files stored in the profile directory is smaller than it should be when generated by newer builds. This is probably affecting more than just Necko.
FYI: I can reproduce this bug on MacOS X 10.3.4 using "Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8a2) Gecko/20040713 Firefox/0.9.1+"
Attached patch v1 patchSplinter Review
OK, this patch solves the problem. Thanks to bryner for explaining why this is needed.
Attachment #153067 - Flags: superreview?(bryner)
Attachment #153067 - Flags: review?(cbiesinger)
Status: REOPENED → ASSIGNED
Priority: -- → P1
Target Milestone: --- → mozilla1.8alpha2
Comment on attachment 153067 [details] [diff] [review] v1 patch r=me, although I can't say I know this chrome registry stuff...
Attachment #153067 - Flags: review?(cbiesinger) → review+
Comment on attachment 153067 [details] [diff] [review] v1 patch a=asa when this is reviewed.
Attachment #153067 - Flags: approval1.8a2+
Attachment #153067 - Flags: superreview?(bryner) → superreview+
fixed-on-trunk
Status: ASSIGNED → RESOLVED
Closed: 21 years ago21 years ago
Resolution: --- → FIXED
Hey.. this fixes the 'brad' tinderbox orangeness that's been occurring for several weeks now. Whee! I'll move it back to the main tinderbox page. I assumed it was a box specific problem since it started occurring coincidental with the box going very flakey (rebooting itself constantly). Thanks!
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: