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)
Tracking
()
VERIFIED
WONTFIX
M5
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.
Updated•26 years ago
|
Status: NEW → ASSIGNED
Comment 2•26 years ago
|
||
per leger, assigning QA contacts to all open bugs without QA contacts according
to list at http://bugzilla.mozilla.org/describecomponents.cgi?product=Browser
Updated•26 years ago
|
Target Milestone: M4
Updated•26 years ago
|
Target Milestone: M4 → M5
Comment 3•26 years ago
|
||
Changed Milestone to M5
Summary: Crash: No error checking on ContentSinkStream or parser → [PP]Crash: No error checking on ContentSinkStream or parser
Updated•26 years ago
|
Status: ASSIGNED → RESOLVED
Closed: 26 years ago
Resolution: --- → WONTFIX
Comment 4•26 years ago
|
||
This is viewer code which is superceded by new code in AppRunner. Changing to
WontFix
Updated•26 years ago
|
QA Contact: 3847 → 4141
Comment 5•26 years ago
|
||
Attempting to steal gem's HTMLParser bugs all at once. Changing QAContact to
janc.
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.
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.
Description
•