Closed Bug 49288 Opened 25 years ago Closed 24 years ago

Crash accessing non existent jar files

Categories

(SeaMonkey :: General, defect, P3)

Product:
SeaMonkey
Component:
General
Platform:
x86
Windows NT
Type:
defect

Tracking

(Not tracked)

Status:
CLOSED FIXED

People

(Reporter: oliver.fels, Assigned: security-bugs)

References

(
URL
)

Details

(Keywords: crash, Whiteboard: [nsbeta3+])

Netscape 6 and M17 running under Windows NT4.0 SP5 immediately crashes, if a non existent jar file is accessed via the jar:http://xxx url.
could you please test a new m18 build? Thanks.
I've tried typing this into the URL bar and it does nothing... 081708 mozilla build on NT
Sorry for not being specific enough, you have to type in an url in a correct format for mozilla to react, like jar:http://www.mozilla.org/test.jar!/test.html If the jar is not present, the browser crashes. Reproduced with build 081708 this morning.
OK. crash reproduceable here on 081708 mozilla win32 build. Talkback report coming soon.
URL: jar:http://everyurl_with_no_jarfile!j... → jar:http://www.mozilla.org/test.jar!/...
Status: UNCONFIRMED → NEW
Ever confirmed: true
warren, is this yours? nsZipReaderCache::ReleaseZip [d:\builds\seamonkey\mozilla\modules\libjar\nsJAR.cpp, line 1201] nsJARChannel::Close [d:\builds\seamonkey\mozilla\netwerk\protocol\jar\src\nsJARChannel.cpp, line 979] nsFileTransport::DoClose [d:\builds\seamonkey\mozilla\netwerk\base\src\nsFileTransport.cpp, line 707] nsFileTransport::Process [d:\builds\seamonkey\mozilla\netwerk\base\src\nsFileTransport.cpp, line 695]
Assignee: asa → warren
Keywords: nsbeta3
Whiteboard: [nsbeta3+]
Adding crash keyword to all open crashers
Keywords: crash
*** Bug 46571 has been marked as a duplicate of this bug. ***
I think my rewrite of the jar protocol will fix this. It should go in this week.
Reassigning to Mitch.
Assignee: warren → mstoltz
Status: NEW → ASSIGNED
Depends on: 24765
Target Milestone: --- → M18
Fix checked in.
Status: ASSIGNED → RESOLVED
Closed: 24 years ago
Resolution: --- → FIXED
Tried this morning and it seems to have vanished. According to my experiencfe one might close the bug . Tried with build 2000092608.
Verified based on Oliver's comments.
Status: RESOLVED → VERIFIED
Can confirm this, though the gap in between is long. Closing the bug, as my reporting mail address will be changing in the very near future.
Status: VERIFIED → CLOSED
Oliver, long time no hear... Please don't mark bugs closed. Your Bugzilla email address can be changed automatically without having to close bugs. Close is used after a product has shipped (which is true in this case, but I think the closing gets done by QA or somebody).
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.