From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 32787] memory leak in radeonReleaseDmaRegions line 340
Date: Sun, 2 Jan 2011 20:27:25 -0800 (PST) [thread overview]
Message-ID: <20110103042725.E6C1513004E@annarchy.freedesktop.org> (raw)
In-Reply-To: <bug-32787-502@http.bugs.freedesktop.org/>
https://bugs.freedesktop.org/show_bug.cgi?id=32787
--- Comment #3 from David Ronis <David.Ronis@McGill.CA> 2011-01-02 20:27:25 PST ---
I'm running the git master (drm, mesa, pixman, & xserver), my libs are also
fairly recent git/master libs (last few weeks). Note that I've been having
this problem for quite some time.
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
next prev parent reply other threads:[~2011-01-03 4:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-02 20:21 [Bug 32787] New: memory leak in radeonReleaseDmaRegions line 340 bugzilla-daemon
2011-01-02 20:24 ` [Bug 32787] " bugzilla-daemon
2011-01-03 1:21 ` bugzilla-daemon
2011-01-03 1:21 ` bugzilla-daemon
2011-01-03 4:27 ` bugzilla-daemon [this message]
2011-03-07 19:30 ` [Bug 32787] [RADEON:KMS:RS300M:R200C] " bugzilla-daemon
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=20110103042725.E6C1513004E@annarchy.freedesktop.org \
--to=bugzilla-daemon@freedesktop.org \
--cc=dri-devel@lists.freedesktop.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;
as well as URLs for NNTP newsgroup(s).