Closed Bug 3023 Opened 26 years ago Closed 26 years ago

[PP]Crash: No error checking on ContentSinkStream or parser

Categories

(Core :: DOM: HTML Parser, defect, P1)

x86
Linux
defect

Tracking

()

VERIFIED WONTFIX

People

(Reporter: akkzilla, Assigned: buster)

Details

On Linux, try a Debug Save in the viewer, change directories (e.g. double-click the .. in the directory list), which nullifies the filename in the filename text field (that's a widget bug which I'll file separately) and click OK. This causes a crash: #0 0x4060907e in nsParser::ResumeParse (this=0x8231490, aDefaultDTD=0x0) at nsParser.cpp:705 #1 0x40608f4e in nsParser::Parse (this=0x8231490, aSourceBuffer=@0xbfffef34, aKey=0x0, anHTMLString=0, aEnableVerify=0, aLastCall=1) at nsParser.cpp:678 #2 0x805fc2f in nsBrowserWindow::DoDebugSave (this=0x81515f0) at nsBrowserWindow.cpp:2823 Apparently there's no sanity checking to make sure that the filename can actually be opened for writing, so even aside from the widget bug on Linux, if a bad filename is entered, the app can crash.
Assignee: rickg → kostello
I'm sharing this lovely bug with you because it's a save issue.
Status: NEW → ASSIGNED
per leger, assigning QA contacts to all open bugs without QA contacts according to list at http://bugzilla.mozilla.org/describecomponents.cgi?product=Browser
Target Milestone: M4
Target Milestone: M4 → M5
Changed Milestone to M5
Summary: Crash: No error checking on ContentSinkStream or parser → [PP]Crash: No error checking on ContentSinkStream or parser
Status: ASSIGNED → RESOLVED
Closed: 26 years ago
Resolution: --- → WONTFIX
This is viewer code which is superceded by new code in AppRunner. Changing to WontFix
QA Contact: 3847 → 4141
Attempting to steal gem's HTMLParser bugs all at once. Changing QAContact to janc.
Status: RESOLVED → VERIFIED
Marking Verified/Won't Fix.
Reassigning all bugs Assigned To kostello to buster
All these bugs were marked "New" when Jan transfered ownership of them to me. They were all resolved and need to be marked "Verified" again.
Status: NEW → RESOLVED
Closed: 26 years ago26 years ago
Status: RESOLVED → VERIFIED
This was Verified on 06/09/99...resetting back to Verified...Bugzilla wacked out.
You need to log in before you can comment on or make changes to this bug.