Closed
Bug 335494
Opened 20 years ago
Closed 17 years ago
leak and eventual crash if <iframe></iframe> with table refreshes many times
Categories
(Firefox :: General, defect)
Tracking
()
RESOLVED
INCOMPLETE
People
(Reporter: y0g1, Unassigned)
References
()
Details
(Keywords: crash, memory-leak)
User-Agent: Mozilla/5.0 (X11; U; NetBSD i386; pl; rv:1.8.0.2) Gecko/20060424 Firefox/1.5.0.2
Build Identifier: Mozilla/5.0 (X11; U; NetBSD i386; pl; rv:1.8.0.2) Gecko/20060424 Firefox/1.5.0.2
There is memory leak during refrashing webpage with <iframe></iframe> and table in it. It is not valid for firefox 1.0.6, but 1.5 crashes on windows, linux and netbsd. You must wait for a long time to get your browser crashed - but it will be done.
Reproducible: Always
Steps to Reproduce:
1. go to page http://83.18.69.154/buggy_firefox/
2. wait...
3. check memory consumption
4. wait...
5. check memory consumption
6. it will be crashed..
Actual Results:
the memory consumption increase
Expected Results:
the memory consumption should stay on the same level
I didn't check it on x86_64 arch
Updated•20 years ago
|
Comment 1•20 years ago
|
||
WFM Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.9a1) Gecko/20060421 Minefield/3.0a1. No noticable increase in memory usage (in Activity Monitor) while the page is active.
Comment 2•20 years ago
|
||
WFM Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.0.2) Gecko/20060308 Firefox/1.5.0.2
I let it run for about 10 minutes and the memory usage never changed by more than 1MB total up or down. In fact, Firefox freed memory during the first few refreshes.
Have you checked the possibility of extensions misbehaving?
| Reporter | ||
Comment 3•20 years ago
|
||
(In reply to comment #2)
> WFM Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.0.2) Gecko/20060308
> Firefox/1.5.0.2
>
> I let it run for about 10 minutes and the memory usage never changed by more
> than 1MB total up or down. In fact, Firefox freed memory during the first few
> refreshes.
>
> Have you checked the possibility of extensions misbehaving?
>
You are right - the main problem is with extension.
I will check which one is broken. After uninstall every extension (polski language pack, mplyer plugin and adblock - the newest versions) memory leak stoped.
Thx for suggestion, I will back to the topic after some more tests
best regards
iu1j4
| Reporter | ||
Comment 4•20 years ago
|
||
> >
> > Have you checked the possibility of extensions misbehaving?
> >
> You are right - the main problem is with extension.
> I will check which one is broken. After uninstall every extension (polski
> language pack, mplyer plugin and adblock - the newest versions) memory leak
> stoped.
actually not stopped - but the leak is very slow. I test it for about 7 hours
and the problem exists but not so big, I will wait if the firefox browser will crash or not.
Before I uninstalled extensions - the browser crashed after about 20 minutes of intensive refreshing the page I listed as an example. (in local network). Now it works 7 hours well, but memory slowly increase. Is it normal?
regards
jarek
| Reporter | ||
Comment 5•20 years ago
|
||
The problem is still valid for firefox 1.5.0.4 without extensions.
I tested mozilla 1.7.13 and I saw no memory leak problem.
Test firefox browser again in your local area network.
The problem is not big but it exists.
Updated•18 years ago
|
Version: unspecified → 1.5.0.x Branch
Comment 6•17 years ago
|
||
reporter, Do you still see this problem. If you do not, please close the bug with resolution WORKSFORME, INVALID, etc as may be appropriate to your situation (but not FIXED unless you know the bug with the patch).
If you still see problem using a current version of Firefox or trunk build, please provide additional detail.
Whiteboard: closeme 2008-12-10
Comment 7•17 years ago
|
||
@Reporter, we have not heard back from you in a while, so I am closing this bug as INCOMPLETE. You can reopen this bug if more information becomes available. Some helpful information you can provide us is found at http://quality.mozilla.org/bug-writing-guidelines.
Status: UNCONFIRMED → RESOLVED
Closed: 17 years ago
Resolution: --- → INCOMPLETE
Whiteboard: closeme 2008-12-10
You need to log in
before you can comment on or make changes to this bug.
Description
•