From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 73127] [r600g] Possible memory leak when playing WoW with CAICOS
Date: Tue, 04 Feb 2014 21:05:25 +0000 [thread overview]
Message-ID: <bug-73127-502-qrea5A8HVa@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-73127-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 543 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=73127
--- Comment #9 from Chris Rankin <rankincj@googlemail.com> ---
The memory leak I'm seeing with my RV790 doesn't seem to occur with this git
revision:
commit f5bd5568abcc234c1c2b6a4bb67b880706f3caed
Author: Mark Mueller <MarkKMueller@gmail.com>
Date: Tue Jan 21 22:37:20 2014 -0800
mesa: Fix Type A _INT formats to MESA_FORMAT naming standard
I am therefore assuming that this is a different bug to #73127.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1394 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2014-02-04 21:05 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-29 18:40 [Bug 73127] New: [r600g] Possible memory leak when playing WoW with CAICOS bugzilla-daemon
2013-12-29 18:47 ` [Bug 73127] " bugzilla-daemon
2014-01-02 17:45 ` bugzilla-daemon
2014-01-02 17:58 ` bugzilla-daemon
2014-01-02 18:18 ` bugzilla-daemon
2014-01-02 18:28 ` bugzilla-daemon
2014-01-02 19:34 ` bugzilla-daemon
2014-01-02 23:35 ` bugzilla-daemon
2014-02-03 21:31 ` bugzilla-daemon
2014-02-04 21:05 ` bugzilla-daemon [this message]
2014-02-12 10:16 ` bugzilla-daemon
2019-09-18 19:12 ` 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=bug-73127-502-qrea5A8HVa@http.bugs.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