Closed Bug 292993 Opened 20 years ago Closed 18 years ago

mozilla buffers every pics, when I browse pages with pics, mozilla consumes all my memory till crash

Categories

(Core :: Graphics: ImageLib, defect)

x86
Windows XP
defect
Not set
critical

Tracking

()

RESOLVED DUPLICATE of bug 213391

People

(Reporter: spectertech, Assigned: pavlov)

References

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.7) Gecko/20050414 MultiZilla/1.7.0.2d
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.7) Gecko/20050414 MultiZilla/1.7.0.2d

When u view some pages with many pics, then mozilla will consume much more
memory than it tends to use. This causes a problem as follow: memory consuming
could exceed to the extent of all ur memory & virtual memory. I think the most
likely causes of this is that mozilla & firefox use some technology as Internet
Explorer buffering pics as their bitmap form. But how can we solve this problem?
Sacrificing the browsing speed to solve the problem? I think it's no need to
sacrifice the speed. We can let the user set the memory max consumption of
memory which can be set to a recommended value. Then surfing online, mozilla can
decide which page buffer the images, which not. So at most situations mozilla
can buffer all the pics, but at some special cases such as browsing tons of
pics, mozilla can also do well, just a little bit slower, & I think slower is
better than hanging there till crash!!! 

Reproducible: Always

Steps to Reproduce:
1.open mozila suite or mozilla firefox
2.use one of them to browse many pages with tons of pics, don't close the pages
u opened before, I think opening 10-20pages is enough. 
3.u can see the memory consumption is surprisingly unbelievable. 

Actual Results:  
u at last to kill the mozilla

Expected Results:  
to find out whether the page consumes too much memory on buffering. If it up to
some extent, the mozilla won't buffer for that page. Memory is limited. If keep
cunsuming as mozilla does now, the memory would be used up & operating system
would use virtuall memory for mozilla's buffering, & that shows no sence for
speed promotion.

I think it's because of the mozilla's buffering module. Just don't buffer
everything can be buffered. The memory is not so big that u can't buffer every pics.
*** Bug 292994 has been marked as a duplicate of this bug. ***
Is this an issue with a trunk build as well?
ftp://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/latest-trunk/
Not a suite issue.  And a duplicate.
Assignee: general → pavlov
Component: General → ImageLib
Product: Mozilla Application Suite → Core
QA Contact: general
Whiteboard: DUPEME
Version: unspecified → Trunk
I have seen the same problem with mozilla 1.7.12
*** This bug has been confirmed by popular vote. ***
Status: UNCONFIRMED → NEW
Ever confirmed: true
I'm seeing what I think is the same problem on FF 1.5

The page http://www.herzlande.de/gallery/slideshow.php?set_albumName=
displays a slideshow of screenshots from games, displaying a new image every 3 seconds.

In top I can watch the amount of memory used by X increase by 2MB every 3 seconds, up to the point where my system becomes completely unresponsive.

If I close the tab containing the slideshow before that happens, the memory usage returns to normal immediately.
(In reply to comment #6)
> I'm seeing what I think is the same problem on FF 1.5
> 
> The page http://www.herzlande.de/gallery/slideshow.php?set_albumName=
> displays a slideshow of screenshots from games, displaying a new image every 3
> seconds.
> 
> In top I can watch the amount of memory used by X increase by 2MB every 3
> seconds, up to the point where my system becomes completely unresponsive.
> 
> If I close the tab containing the slideshow before that happens, the memory
> usage returns to normal immediately.

That sounds like a different problem that's likely happening only on Unix systems. If you can still reproduce the problem, please file a new bug report about it.

The original bug, that Mozilla stores all images in currently open pages uncompressed in the memory cache, is the same as bug 213391.

*** This bug has been marked as a duplicate of 213391 ***
Status: NEW → RESOLVED
Closed: 18 years ago
Resolution: --- → DUPLICATE
Whiteboard: DUPEME
You need to log in before you can comment on or make changes to this bug.