From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 74539] [r600g] Memory leak when playing WoW with RV790 Date: Wed, 16 Apr 2014 07:22:17 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0597527404==" Return-path: Received: from culpepper.freedesktop.org (unknown [131.252.210.165]) by gabe.freedesktop.org (Postfix) with ESMTP id 477B66EA07 for ; Wed, 16 Apr 2014 00:22:17 -0700 (PDT) In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dri-devel-bounces@lists.freedesktop.org Sender: "dri-devel" To: dri-devel@lists.freedesktop.org List-Id: dri-devel@lists.freedesktop.org --===============0597527404== Content-Type: multipart/alternative; boundary="1397632937.1BCd06E1.25103"; charset="us-ascii" --1397632937.1BCd06E1.25103 Date: Wed, 16 Apr 2014 07:22:17 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable https://bugs.freedesktop.org/show_bug.cgi?id=3D74539 --- Comment #34 from Michel D=C3=A4nzer --- (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 C= PU > 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 fr= om 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 lea= ks, so valgrind should be the proper tool for the job. --=20 You are receiving this mail because: You are the assignee for the bug. --1397632937.1BCd06E1.25103 Date: Wed, 16 Apr 2014 07:22:17 +0000 MIME-Version: 1.0 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable

Commen= t # 34 on bug 74539<= /a> from Michel D=C3=A4nzer 
(In reply to comment #=
33)
> This is the Xorg.0.log file from an instance whe=
re I didn't get
> keyboard/mouse control back at all, and Xorg just chewed up 100% of on=
e 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 fr=
om
it.


(In reply to comment #32)
> Perhaps not, but possibly worth asking Mr Greg K=
H 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 lea=
ks,
so valgrind should be the proper tool for the job.

You are receiving this mail because: =20=20=20=20=20=20
  • You are the assignee for the bug.
--1397632937.1BCd06E1.25103-- --===============0597527404== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel --===============0597527404==--