From: David Ashley <dash@xdr.com>
To: linux-kernel@vger.kernel.org
Subject: Re: Cached memory never gets released [SOLVED!!!]
Date: Tue, 29 Jun 2004 09:57:10 -0700 [thread overview]
Message-ID: <200406291657.i5TGvARd028334@xdr.com> (raw)
I've located the source of the leak.
Linux is innocent! Sorry for doubting you.
The problem is mozilla/flash allocates shared memory
segments but doesn't get a chance to clean them up properly.
So:
Flash memory leak is present related to japanese fonts and our
particular flash content.
We've installed a watchdog process that kills mozilla and
restarts it once it uses up too much memory.
The watchdog process kills mozilla so mozilla doesn't have an
opportunity to free up its shared memory allocations.
They build up over time:
------ Shared Memory Segments --------
key shmid owner perms bytes nattch status
0x00000000 3014673 root 666 1920000 0
0x00000000 1310738 root 666 1920000 0
0x00000000 2162707 root 666 1920000 0
0x00000000 5537812 root 666 1920000 0
0x00000000 3866645 root 666 1920000 0
0x00000000 4718614 root 666 1920000 0
When I ipcrm these the cached memory goes back down to normal levels.
Thanks for everyone who responded, and sorry for wasting everyone's time.
-Dave
reply other threads:[~2004-06-29 16:57 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200406291657.i5TGvARd028334@xdr.com \
--to=dash@xdr.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.