David Baron :dbaron: Reporter
	Description • 24 years ago

If the last release of a document viewer is during JS GC, it causes a JS
assertion because the call to SetStatus and SetDefaultStatus from
GlobalWindowImpl::SetNewDocument leads to a call to js_AllocGCThing.  This also
shouldn't be happening during destruction, since the JS GC could hold the
document viewer well past when the new document is displayed.  We're changing JS
code soon to clear up the tinderbox orange resulting from this...

Perhaps these calls should be moved into DocumentViewerImpl::Stop (from
GlobalWindowImpl::SetNewDocument)?

	David Baron :dbaron: Reporter
	Comment 2 • 24 years ago

r=dbaron

	Peter "jag" Annema
	Comment 4 • 24 years ago

r=jag

	Brendan Eich [:brendan]
	Comment 5 • 24 years ago

sr=brendan@mozilla.org

And someone needs to fix nsDocumentViewer.cpp so its dtor does not assume where
and when the last Release is called.

/be

	Peter "jag" Annema
	Comment 6 • 24 years ago

dbaron checked this patch in. More to follow?

	David Baron :dbaron: Reporter
	Comment 7 • 24 years ago

See patch in bug 61821 for more (regarding brendan's comments).

	Johnny Stenback (:jst) Assignee
	Comment 8 • 24 years ago

I believe this is fixed by dbarons checkin, marking FIXED.

	Prashant Desale
	Comment 9 • 24 years ago

Verified with 2001-020608.