dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 83022] memory leak
Date: Mon, 25 Aug 2014 08:28:49 +0000	[thread overview]
Message-ID: <bug-83022-502-rk8kPWSwNG@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-83022-502@http.bugs.freedesktop.org/>


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

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

--- Comment #5 from pavol@klacansky.com ---
I tried to run it with valgrind and there are so many errors and it just
crashed whole system (I mean disk IO was so high I had to press shutdown
button, I do not get this, as I had no swap enabled). Second time I tried it
and killed it just before system run out of resources. It looked like system
works, however, Xorg process used all CPU (driver crashed and switched to SW
rendering?) even that glxinfo reported it is running on R600.

On Intel driver it works well (I have dual system).

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

[-- Attachment #1.2: Type: text/html, Size: 1341 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-08-25  8:28 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-24 21:02 [Bug 83022] New: memory leak bugzilla-daemon
2014-08-25  1:45 ` [Bug 83022] " bugzilla-daemon
2014-08-25  7:59 ` bugzilla-daemon
2014-08-25  7:59 ` bugzilla-daemon
2014-08-25  8:00 ` bugzilla-daemon
2014-08-25  8:28 ` bugzilla-daemon [this message]
2014-08-26  3:12 ` bugzilla-daemon
2019-09-18 19:17 ` 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-83022-502-rk8kPWSwNG@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