All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 74539] [r600g] Memory leak when playing WoW with RV790
Date: Wed, 16 Apr 2014 07:22:17 +0000	[thread overview]
Message-ID: <bug-74539-502-471MTTlWQx@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-74539-502@http.bugs.freedesktop.org/>


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

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

--- Comment #34 from Michel Dänzer <michel@daenzer.net> ---
(In reply to comment #33)
> This is the Xorg.0.log file from an instance where I didn't get
> keyboard/mouse control back at all, and Xorg just chewed up 100% of one CPU
> instead.

DRICloseScreen is a DRI1 function; I suspect the backtraces in the Xorg log
file aren't reliable. It would be interesting to see where the Xorg process is
spinning, e.g. by attaching gdb to it and getting a couple of backtraces from
it.


(In reply to comment #32)
> Perhaps not, but possibly worth asking Mr Greg KH if he'd be prepared to
> consider it anyway?

Sure, feel free to ask him. :)

Anyway, any GPU resource leaks should be accompanied by 'normal' memory leaks,
so valgrind should be the proper tool for the job.

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

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

  parent reply	other threads:[~2014-04-16  7:22 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-04 21:12 [Bug 74539] New: [r600g] Memory leak when playing WoW with RV790 bugzilla-daemon
2014-02-08 15:21 ` [Bug 74539] " 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 [this message]
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-471MTTlWQx@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.