Closed Bug 63642 Opened 24 years ago Closed 24 years ago

Crash when type .0html instead of .html

Categories

(Core :: Networking: File, defect)

x86
Windows NT
defect
Not set
critical

Tracking

()

VERIFIED DUPLICATE of bug 66330
mozilla0.9

People

(Reporter: bugs4hj, Assigned: dougt)

References

Details

(Keywords: crash, hang)

Attachments

(1 file)

Used build 2000122004 on WinNT4 Sp6b. (will test with the latest build a.s.a.p.) Steps to reproduce: (always at least in my case) Type in something like: http://www.foo.0html Result: Mozilla crashes (Dr. watson window) Expected result: Message like Netscape 4.76 I think this is 'critical', because human typo's may occur frequently. Sorry, but I'm in a protected environment, and not aloud to send you any logs!
Add keyword crash
Keywords: crash
wfm win98 CVS 2000-12-22
worksforme buildID 2000122204 win32. www.foo.0html and www.foo.com/bar.0html both produce the expected results -- server not found and page not found on server.
Add. info, build 2000122220 same problem. CPU almost 100% on Pentium 350MHz. Startpage called start.html on a local E: drive in this case.
i cannot see this as well. Reporter, please try the following: 1) does this happen with a new proflie (mozilla -profilemanger) 2) with a new build? thanks!
Worksforme 122604 mozilla win32 build on NT, 122610 mozilla linux build on RedHat6.2, 122609 mozilla mac build on OS9.
Status: UNCONFIRMED → RESOLVED
Closed: 24 years ago
Resolution: --- → WORKSFORME
Sorry but this still crashes my system! Please try something like this: file:///e|/startpages/start.0html I have a brandnew system, first time Mozilla build 2000122920 install. But still the problem, sorry, so reopening this bug!
Status: RESOLVED → UNCONFIRMED
Resolution: WORKSFORME → ---
over to Networking for a look. Steps to reproduce (for me) were a little more specific than originally reported. Here's the steps I had to take to get the CPU to spike to 100% causing an application hang, not a crash. 1. open browser 2. load http URL 3. paste or type file:///e|/startpages/start.0html into URL field 4. hit enter. with these steps i can repro consistently. If however I type a valid file URL (rather than an http URL) in and then type the .0hmtl file URL I am unable to reproduce the problem. tested with 122904 mozilla build on NT
Assignee: asa → neeti
Status: UNCONFIRMED → NEW
Component: Browser-General → Networking
Ever confirmed: true
Keywords: hang
QA Contact: doronr → tever
Asa, I use this type of url's a lot, for testcases/examples. I save testcases from bugzilla to a local drive like this: e:\mozilla\smxxxxx-y.html. Where sm = sea monkey and xxxxx = bugnumber and y = the index number of the testcase. o for original, 1 and ++ after a change. After saving this from Bugzilla, Netscape/Mozilla change the filename into something like this: file:///e|/smxxxxx-y.html (e: (actual x) is my xdrive). After making changes to the file, I have to changing the y in 1,2,3,4,5, and so on. And by doing this, I sometimes ran into this problem. It are my stupid mistakes, that's for sure, but Mozilla should not crash. And Asa, system crash should read 'Mozilla crash'.
*** Bug 64505 has been marked as a duplicate of this bug. ***
changing component to Networking:file
Assignee: neeti → dougt
Component: Networking → Networking: File
Keywords: nsbeta1
Target Milestone: --- → mozilla0.9
can;t reproduce. Can someone try to get a stackcrawl. The DR Watson log looks like we are crashing in NS_ShutdownXPCOM, but also ExtractURLScheme is in the log.
Keywords: qawanted
Marking as a dup. *** This bug has been marked as a duplicate of 66330 ***
Status: NEW → RESOLVED
Closed: 24 years ago24 years ago
Resolution: --- → DUPLICATE
verified dup
Status: RESOLVED → VERIFIED
Keywords: qawanted
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: