Closed
Bug 204283
Opened 21 years ago
Closed 21 years ago
UMR in CNavDTD.cpp - enabled not set by nsHTMLFragmentContentSink::IsEnabled()
Categories
(Core :: DOM: HTML Parser, defect)
Tracking
()
VERIFIED
DUPLICATE
of bug 230536
People
(Reporter: ajschult784, Unassigned)
Details
Attachments
(1 file)
229 bytes,
text/html
|
Details |
CNavDTD::WillBuildModel calls mSink->IsEnabled and expects it to set |enabled|, and while nsHTMLContentSink::IsEnabled will always set it, nsHTMLFragmentContentSink::IsEnabled never sets it (it just returns NS_OK). Valgrind complains about this. http://lxr.mozilla.org/mozilla/source/htmlparser/src/CNavDTD.cpp#427 I'll attach a simple testcase that triggers this. This occurs with today's linux CVS trunk.
Reporter | ||
Comment 1•21 years ago
|
||
Updated•21 years ago
|
Flags: blocking1.6?
Summary: UMR in CNavDTD.cpp - enabled not set by nsHTMLFragmentContentSinkIsEnabled() → UMR in CNavDTD.cpp - enabled not set by nsHTMLFragmentContentSink::IsEnabled()
Comment 2•21 years ago
|
||
hmmmm.... I tried this fix but it didn't fix bug 228688 so maybe this isn't the cause of 228688 (directly) [the timing doesn't seem right anyways]: Index: nsHTMLFragmentContentSink.cpp =================================================================== RCS file: /cvsroot/mozilla/content/html/document/src/nsHTMLFragmentContentSink.cpp,v retrieving revision 1.79 diff -r1.79 nsHTMLFragmentContentSink.cpp 102c102 < NS_IMETHOD IsEnabled(PRInt32 aTag, PRBool* aReturn) { return NS_OK; } --- > NS_IMETHOD IsEnabled(PRInt32 aTag, PRBool* aReturn) { *aReturn = PR_FALSE; return NS_OK; }
Comment 3•21 years ago
|
||
so if not related to the problem in bug 228688 , should the 1.6 nomination hang around... other than Valgrind errors are we seeing places where bad things are happinging... also not clear from the comments... did errors just show up on 2003-05-02 or were they around before?
Reporter | ||
Comment 4•21 years ago
|
||
> other than Valgrind errors are we seeing places where bad things are > happinging. I don't know of any other symptom for this bug other than the Valgrind error (there are no user-visible symptoms). > also not clear from the comments... did errors just show up on 2003-05-02 or > were they around before? I only noticed the problem on 5/2/03. I don't know if it started before that or not (valgrind doesn't give much useful info from a stripped (default nightly) build). That is before bug 228688 started happening (7/1/03).
Assignee: harishd → parser
QA Contact: dsirnapalli → nobody
You need to log in
before you can comment on or make changes to this bug.
Description
•