All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 74539] New: [r600g] Memory leak when playing WoW with RV790
Date: Tue, 04 Feb 2014 21:12:35 +0000	[thread overview]
Message-ID: <bug-74539-502@http.bugs.freedesktop.org/> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 1571 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=74539

          Priority: medium
            Bug ID: 74539
          Assignee: dri-devel@lists.freedesktop.org
           Summary: [r600g] Memory leak when playing WoW with RV790
          Severity: normal
    Classification: Unclassified
                OS: Linux (All)
          Reporter: rankincj@googlemail.com
          Hardware: x86-64 (AMD64)
            Status: NEW
           Version: git
         Component: Drivers/Gallium/r600
           Product: Mesa

Created attachment 93417
  --> https://bugs.freedesktop.org/attachment.cgi?id=93417&action=edit
dmesg log showing memory allocation failure.

I am seeing a possible memory leak while playing WoW-64.exe with my RV790. The
problem seems to happen after ~ 1 hour of play:

[  117.896993] fuse init (API version 7.22)
[ 3326.401752] WoW-64.exe: page allocation failure: order:4, mode:0x10c0d0
[ 3326.407099] CPU: 7 PID: 31106 Comm: WoW-64.exe Not tainted 3.12.9 #1
[ 3326.412185] Hardware name: Gigabyte Technology Co., Ltd.
EX58-UD3R/EX58-UD3R, BIOS FB  05/04/2009
[ 3326.419812]  ffff8801afdcdbd0 ffffffff812d0071 0000000000000001
ffffffff810a0c50
[ 3326.426142]  0000000000000001 0000000000000000 ffffffff8164ff80
ffffffff8164f400
[ 3326.432429]  000000000010c0d0 ffffffff812cebb7 ffffffff8164f400
ffff880100000000

I *think* I can bisect this, although it might make some time:

9bace99d77642f8fbd46b1f0be025ad758f83f5e        BAD
f5bd5568abcc234c1c2b6a4bb67b880706f3caed        GOOD

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 3053 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

             reply	other threads:[~2014-02-04 21:12 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-04 21:12 bugzilla-daemon [this message]
2014-02-08 15:21 ` [Bug 74539] [r600g] Memory leak when playing WoW with RV790 bugzilla-daemon
2014-02-08 15:36 ` bugzilla-daemon
2014-02-08 16:13 ` bugzilla-daemon
2014-03-02  0:48 ` bugzilla-daemon
2014-03-03 10:22 ` bugzilla-daemon
2014-03-03 11:31 ` bugzilla-daemon
2014-03-03 14:29 ` bugzilla-daemon
2014-03-03 14:35 ` bugzilla-daemon
2014-03-03 21:54 ` bugzilla-daemon
2014-03-03 22:33 ` bugzilla-daemon
2014-03-04 21:40 ` bugzilla-daemon
2014-03-04 22:16 ` bugzilla-daemon
2014-03-05  4:10 ` bugzilla-daemon
2014-03-05  4:10 ` bugzilla-daemon
2014-03-05  4:12 ` bugzilla-daemon
2014-03-05  4:12 ` bugzilla-daemon
2014-03-05 16:53 ` bugzilla-daemon
2014-03-05 17:31 ` bugzilla-daemon
2014-03-06  6:54 ` bugzilla-daemon
2014-03-06 21:32 ` bugzilla-daemon
2014-03-06 21:43 ` bugzilla-daemon
2014-03-06 21:45 ` bugzilla-daemon
2014-03-06 21:46 ` bugzilla-daemon
2014-03-06 21:47 ` bugzilla-daemon
2014-03-06 21:48 ` bugzilla-daemon
2014-03-06 21:50 ` bugzilla-daemon
2014-03-06 21:51 ` bugzilla-daemon
2014-03-06 22:00 ` bugzilla-daemon
2014-04-07 21:51 ` bugzilla-daemon
2014-04-09  6:33 ` bugzilla-daemon
2014-04-09  7:50 ` bugzilla-daemon
2014-04-10 21:01 ` bugzilla-daemon
2014-04-10 21:11 ` bugzilla-daemon
2014-04-10 21:29 ` bugzilla-daemon
2014-04-11 10:45 ` bugzilla-daemon
2014-04-11 14:15 ` bugzilla-daemon
2014-04-13 23:25 ` bugzilla-daemon
2014-04-16  7:22 ` bugzilla-daemon
2014-04-18 23:09 ` bugzilla-daemon
2014-04-21  6:50 ` bugzilla-daemon
2014-04-29 18:20 ` bugzilla-daemon
2019-09-18 19:14 ` 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-74539-502@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.