Closed Bug 120253 Opened 24 years ago Closed 23 years ago

Fix leaks and occasional crashes of the combination generated content/content model view

Categories

(Core :: XUL, defect)

x86
Linux
defect
Not set
critical

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: janv, Assigned: janv)

Details

(Keywords: crash, memory-leak)

I noticed when I closed a window with generated content that content view's dtor was not called. I works fine elsewhere, e.g. Preferences. And I also crashed later. I also noticed one thing. nsXULDocument::CheckTemplateBuilder() doesn't bail out for rdfliner, since rdfliner doesn't set "database" attribute.
I originaly changed GetDatabase() check to GetTemplateBuilderFor() as part of the syntax change, but then I realized that it might cause problems.
Status: NEW → ASSIGNED
Severity: normal → critical
Keywords: crash, mlk
The rdfliner calls SetTemplateBuilderFor at (around) nsXULDocument.cpp:6401 -- shouldn't that suffice?
yes, you are right, but ... If I don't check for already created and appended <outlinerchildren> in nsXULDocument::CheckTemplateBuilder() I get 2 <outlinerchildren>s and 2 outliner body frames of course, it looks really weird. So I think SetTemplateBuilderFor() is called, but database attribute is present later It doesn't create 2 tags when I replace GetDatabase() check with GetTemplateBuilderFor() in nsXULDocument::CheckTemplateBuilder()
It seems that this is not an issue anymore. I don't see it. Probably waterson's fix for 86755. Marking WFM.
Status: ASSIGNED → RESOLVED
Closed: 23 years ago
Resolution: --- → WORKSFORME
Component: XP Toolkit/Widgets: Trees → XUL
QA Contact: jrgmorrison → xptoolkit.widgets
You need to log in before you can comment on or make changes to this bug.