Glancing at the code and Bugzilla it looks like a leak in FF's js code dealing with events. Seems to be new with 1.5. If an event is referenced by something from the document its instance counters increment artificially. (or increment without anyone claiming responsibility to decrement.) The object is never destroyed until close which is where Leak Monitor flags it. The js code could work around it but shouldn't need to. It's really a FF thing. Have you tried this with 1.5.0.4? Not much else you can do but try a nightly build. (looks like the fixes are in flux.)
Leak monitor doesn't know enough to tell where the problems lie. Good to make sure your extensions behave, or to home in on FF bugs, but most users would be doing chicken-blinks.
__________________
There are a vast number of people who are uninformed and heavily propagandized, but fundamentally decent. The propaganda that inundates them is effective when unchallenged, but much of it goes only skin deep. If they can be brought to raise questions and apply their decent instincts and basic intelligence, many people quickly escape the confines of the doctrinal system and are willing to do something to help others who are really suffering and oppressed." -Manufacturing Consent: Noam Chomsky and the Media, p. 195
|