From: Patrick Plattes <patrick@erdbeere.net>
To: linux-kernel@vger.kernel.org
Cc: Aleksander Pavic <aleksander.pavic@t-online.de>
Subject: Memory leak with 2.6.12 and cdrecord
Date: Tue, 5 Jul 2005 13:33:43 +0200 [thread overview]
Message-ID: <20050705113343.GA6349@erdbeere.net> (raw)
Hi Ho :-),
we have some trouble with the 2.6v kernel tree and CDRecord 2.01 (Debian
Sarge package). If we try to write an 150MB CD the memory fills up to
150MB. The memory will not deallocate after closing cdrecord. Next if we
try to write an 200MB CD the memory will filled up to additional 50MB.
We don't know which part of the software is steals our memory. This only
happens on 2.6, not on an 2.4 system and we can reproduce the bug only
on the asus notebook.
We have tried to find the leak with top and slabtop, but inconclusively. I
put some information together. The informations are taken from the system
after burning a 154MB CD. Please have a look at: http://cdrecord.sourcecode.cc .
I uploaded the files to this address, to avoid high traffic on the lkml.
Thanks for help,
Patrick
next reply other threads:[~2005-07-05 11:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-05 11:33 Patrick Plattes [this message]
2005-07-05 12:06 ` Memory leak with 2.6.12 and cdrecord Jens Axboe
2005-07-05 15:50 ` Patrick Plattes
2005-07-06 23:20 ` Andrew Morton
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=20050705113343.GA6349@erdbeere.net \
--to=patrick@erdbeere.net \
--cc=aleksander.pavic@t-online.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox