270767 - Mozilla crashed

Status: RESOLVED EXPIRED

(SeaMonkey :: General, defect)

Description

[Vano Beridze]

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.3) Gecko/20040922
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.3) Gecko/20040922

Mozilla crashed after I started VMWare workstation.
cat /var/log/messages

Nov 19 11:28:33 iguana kernel: Free pages:        6036kB (0kB HighMem)
Nov 19 11:28:33 iguana kernel: Active:185098 inactive:63612 dirty:6555 writeback
:2397 unstable:0 free:1509 slab:4571 mapped:147675 pagetables:662
Nov 19 11:28:35 iguana kernel: DMA free:3852kB min:12kB low:24kB high:36kB activ
e:0kB inactive:8832kB present:16384kB
Nov 19 11:28:35 iguana kernel: protections[]: 0 0 0
Nov 19 11:28:33 iguana gconfd (vanob-3912): GConf server is not in use, shutting
 down.
Nov 19 11:28:36 iguana kernel: Normal free:2184kB min:1004kB low:2008kB high:301
2kB active:740392kB inactive:245616kB present:1032176kB
Nov 19 11:28:36 iguana kernel: protections[]: 0 0 0
Nov 19 11:28:36 iguana kernel: HighMem free:0kB min:128kB low:256kB high:384kB a
ctive:0kB inactive:0kB present:0kB
Nov 19 11:28:36 iguana kernel: protections[]: 0 0 0
Nov 19 11:28:36 iguana gconfd (vanob-3912): Exiting
Nov 19 11:28:36 iguana kernel: DMA: 539*4kB 170*8kB 21*16kB 0*32kB 0*64kB 0*128k
B 0*256kB 0*512kB 0*1024kB 0*2048kB 0*4096kB = 3852kB
Nov 19 11:28:36 iguana kernel: Normal: 0*4kB 1*8kB 0*16kB 10*32kB 13*64kB 0*128k
B 0*256kB 0*512kB 1*1024kB 0*2048kB 0*4096kB = 2184kB
Nov 19 11:28:36 iguana kernel: HighMem: empty
Nov 19 11:28:36 iguana kernel: Swap cache: add 5871, delete 4126, find 1958/2152
, race 0+0
Nov 19 11:28:36 iguana kernel: Out of Memory: Killed process 4983 (mozilla-bin).

As you can see mozilla-bin was killed because of out of memory.
So there is a memory leak.
I've got 1GB ram, 1GB Swap.
I usualy open Mozilla mail and a browser.
I've got a bookmarks group containing about 30 links.
So when I open 30 tabs simaltenously mozilla really eats a memory.
If I close all of the instances of mozilla I can see that the memory usage
is really low.

Reproducible: Sometimes
Steps to Reproduce:
1.
2.
3.

Comment 1

[Mitch]

So what is the memory use of mozilla ? And how exactly are you monitoring the
memory of the process ? A memory leak is only when memory is not being freed
when it is no longer referenced. If you opened 30 tabs each with some content, i
would expect your memory consumption would grow. You don't mention what other
processes are running also on your system. The OOM killer with randomly chose a
process to murder. If you want determinstic behavior, set your user stacksize
limit using limit/ulimit appropriately.

Comment 2

[Gervase Markham [:gerv]]

This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/

Comment 3

[Gervase Markham [:gerv]]

This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.