From: bugtrack@alsa-project.org
To: alsa-devel@alsa-project.org
Subject: [ALSA - driver 0001823]: surround40 memory leak
Date: Mon, 6 Feb 2006 06:32:18 +0100 [thread overview]
Message-ID: <5447e22bd08973ffc699ce9a85a853e9@bugtrack.alsa-project.org> (raw)
A NOTE has been added to this issue.
======================================================================
<https://bugtrack.alsa-project.org/alsa-bug/view.php?id=1823>
======================================================================
Reported By: darkbrain
Assigned To:
======================================================================
Project: ALSA - driver
Issue ID: 1823
Category: PCI - cs46xx
Reproducibility: always
Severity: major
Priority: normal
Status: new
Distribution:
Kernel Version:
======================================================================
Date Submitted: 02-05-2006 22:59 CET
Last Modified: 02-06-2006 06:32 CET
======================================================================
Summary: surround40 memory leak
Description:
It seems that surround40 has a memory leak or somthing similar, playing a
game in surround40 mode the game result unplayable after some minutes.
And there is a problem in CS46xx.conf file, i need to remove the hook on
the rear pcm to permit multiple surround40 subdevices to be opened.
======================================================================
----------------------------------------------------------------------
Raymond - 02-06-06 06:32
----------------------------------------------------------------------
How do the driver support Surround40 ?
static struct snd_pcm_hardware snd_cs46xx_playback =
{
.channels_min = 1,
.channels_max = 2,
Issue History
Date Modified Username Field Change
======================================================================
02-05-06 22:59 darkbrain New Issue
02-06-06 06:32 Raymond Note Added: 0007943
======================================================================
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
next reply other threads:[~2006-02-06 5:32 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-06 5:32 bugtrack [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-08-03 2:26 [ALSA - driver 0001823]: surround40 memory leak bugtrack
2006-08-01 4:39 bugtrack
2006-08-01 1:52 bugtrack
2006-08-01 0:48 bugtrack
2006-07-31 20:52 bugtrack
2006-07-31 20:42 bugtrack
2006-07-31 3:39 bugtrack
2006-07-30 9:53 bugtrack
2006-07-30 1:33 bugtrack
2006-07-30 1:26 bugtrack
2006-07-29 20:44 bugtrack
2006-07-29 15:23 bugtrack
2006-07-29 13:01 bugtrack
2006-07-29 12:50 bugtrack
2006-07-29 12:12 bugtrack
2006-07-29 12:02 bugtrack
2006-07-29 10:23 bugtrack
2006-07-29 10:20 bugtrack
2006-07-29 3:13 bugtrack
2006-07-28 3:03 bugtrack
2006-07-26 14:26 bugtrack
2006-07-26 7:45 bugtrack
2006-07-26 6:34 bugtrack
2006-07-26 0:21 bugtrack
2006-07-25 18:29 bugtrack
2006-07-25 14:03 bugtrack
2006-07-25 8:18 bugtrack
2006-07-25 0:41 bugtrack
2006-07-24 19:25 bugtrack
2006-07-24 19:21 bugtrack
2006-07-11 11:28 bugtrack
2006-03-27 2:42 bugtrack
2006-02-21 6:56 bugtrack
2006-02-15 5:21 bugtrack
2006-02-12 4:09 bugtrack
2006-02-11 14:01 bugtrack
2006-02-06 17:37 bugtrack
2006-02-06 9:46 bugtrack
2006-02-06 9:46 bugtrack
2006-02-05 21:59 bugtrack
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=5447e22bd08973ffc699ce9a85a853e9@bugtrack.alsa-project.org \
--to=bugtrack@alsa-project.org \
--cc=alsa-devel@alsa-project.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