Closed Bug 323266 Opened 19 years ago Closed 12 years ago

Invoking find as you type leaks the window

Categories

(SeaMonkey :: Find In Page, defect)

x86
Linux
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED INCOMPLETE

People

(Reporter: ajschult784, Unassigned)

References

()

Details

(Keywords: helpwanted, memory-leak)

If I load just about any page and invoke find-as-you-type, dbaron's new leak logging says: Leaked inner window 88864c0 (outer 87bb228) at address 88864c0. ... with URI "http://www.google.com/". Leaked outer window 87bb228 at address 87bb228. I tried a local copy of www.google.com, but got no leak. I also got no leak invoking FAYT at http://www.mozilla.org/
Oh, that was with SeaMonkey trunk 20060112. Firefox also leaks the document: Leaked document at address 968b380. ... with URI "http://www.google.com/".
possibly a dupe of bug 321283?
sorry. can't be - that was checked in on the 10th and the build here was from the 12th. maybe bug 315708 then?
It looks like the relevant code is very forked, so it's probably best to keep these separate.
Keywords: helpwanted
Shouldn't this be in product:Mozilla Application Suite rather than product:Core, then?
If bugzilla component organization was sane, then yes. But it's not. SeaMonkey has multiple components still in Core (Tabbed Browser, Location Bar, etc). Toolkit FAYT is Firefox:Find Toolbar/Fastfind (also the wrong product).
Assignee: aaronleventhal → nobody
Product: Core → SeaMonkey
Is there actual steps to reproduce? AFAIK the memory management, leak logging, JS engine and much more were rewritten (so as tons of Google JS) since 2006. So I suggest to close the bug as 'expired and noone wants to check it again'.
> So I suggest to close the bug as 'expired and noone wants to check it again'. Closing as INCOMPLETE.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.