From: "Steven E. Woolard" <tuxq@tuxq.com>
To: linux-kernel@vger.kernel.org
Subject: PROBLEM: ATAPI (Memory Leak?)
Date: Wed, 25 Aug 2004 00:42:58 -0400 [thread overview]
Message-ID: <412C18D2.5080206@tuxq.com> (raw)
After an attempt to burn an AUDIO CD using IDE (not scsi emulation)
the AUDIO CD played back on a regular cd-player only to have some very
weird sounds.
Also, it might be a possible memory leak issue as well.
After doing this, I noticed my memory usage was at 730MB+ (of 1024MB)
Which is very far from normal (150MB)...
So I rebooted, and burned another audio-cd ... in hope of it was the way
I obtained the WAV files (xmms diskwrite plugin)... I was wrong...
Memory usage shot through the roof again... AUDIO CD was another coaster
burn....
If this has been fixed in an rc or mm patch, let me know--I'll upgrade
As for now, I'm back on 2.6.7
As a side note: 2.6.7 burns Audio CD's just fine... memory usage also
stays normal.
next reply other threads:[~2004-08-25 4:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-25 4:42 Steven E. Woolard [this message]
2004-08-25 4:49 ` PROBLEM: ATAPI (Memory Leak?) Lee Revell
2004-08-25 14:40 ` Ben Duncan
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=412C18D2.5080206@tuxq.com \
--to=tuxq@tuxq.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox