Closed Bug 264660 Opened 20 years ago Closed 20 years ago

"find" sometimes causes memory usage to explode

Categories

(SeaMonkey :: General, defect)

x86
Windows 2000
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED INVALID

People

(Reporter: bigcactus, Unassigned)

References

()

Details

(Keywords: memory-leak)

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.1) Gecko/20040707
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.1) Gecko/20040707

tried to find "critic" and it sits there consuming huge quantities of memory. 
have seen this before on other pages.  since this url changes constantly you may
not be able to reproduce.

Reproducible: Always
Steps to Reproduce:
1.
2.
3.
You mean find as Find In This Page...?
Keywords: mlk
bigcactus, you need to provide a precise defined html page: best would be a
reduced testcase. And you need to provide the data, output of a memory
management tool somehow. You just can't claim memory leakages like that, without
substantiating your claim. Some available are listed here:

http://www.mozilla.org/projects/xpcom/MemoryTools.html

Also, your bug report is contradictory. Your summary suggests that a problem
happens "sometimes" and your description says "Reproducible: Always".
Your using a 3 months old 1.7 branch build while you've chosen Version: Trunk:
"be sure that you've reproduced your bug using a build released within the past
three days. Our development process moves at lightning speed, and the bug you've
found may already have been fixed."
http://www.mozilla.org/quality/bug-writing-guidelines.html

FWIW, searching (Ctrl+F) for "critic" in the page at the url WORKSFORME without
problems with Mozilla 1.8a5 build 2004101505; XP Pro SP2 here.

Note that that tv.yahoo.com page has over 7500 validation errors no matter which
doctype declaration you might use. The page has huge markup coding problems no
matter what.

I will resolve this bug as WORKSFORME unless I hear details, explanations,
clarifications from you.
yet another problem caused by an extension, this time the preferences toolbar.
i have had nothing but problems with them.  should have guessed it first, but it
seemed an unlikely relationship.
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → INVALID
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.