All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 74868] r600g: Diablo III Crashes After a few minutes
Date: Sat, 29 Mar 2014 20:44:24 +0000	[thread overview]
Message-ID: <bug-74868-502-0imuftvrQv@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-74868-502@http.bugs.freedesktop.org/>


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

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

--- Comment #17 from Nick Tenney <nick.tenney@gmail.com> ---
(In reply to comment #14)
> Created attachment 95909 [details] [review]
> r600g: Don't leak bytecode on shader compile failure
> 
> Does this patch help?

Finally had a chance to test the patch. I compiled this morning with and
without the patch and GALLIUM_HUD=fps,requested-VRAM,requested-GTT. It clearly
leaked away without and the flow was stemmed with the proper error handling
patch. Awesome!

I see that the patch properly destroys the shader on error now, which is
definitely an improvement. The error spamming to stdout is still occurring, so
I'm not sure whether that should be another bug report/left open in this one
with a new name or anything.

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

[-- Attachment #1.2: Type: text/html, Size: 2034 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-03-29 20:44 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-12  2:20 [Bug 74868] New: r600g: Diablo III Crashes After a few minutes bugzilla-daemon
2014-02-12  2:20 ` [Bug 74868] " bugzilla-daemon
2014-02-12  2:21 ` bugzilla-daemon
2014-02-12  2:26 ` bugzilla-daemon
2014-02-12  8:10 ` bugzilla-daemon
2014-02-13  3:26 ` bugzilla-daemon
2014-02-15 17:37 ` bugzilla-daemon
2014-02-15 20:33 ` bugzilla-daemon
2014-02-16  2:05 ` bugzilla-daemon
2014-02-16  4:15 ` bugzilla-daemon
2014-02-16 17:21 ` bugzilla-daemon
2014-02-17  3:29 ` bugzilla-daemon
2014-02-21  3:24 ` bugzilla-daemon
2014-03-07  3:49 ` bugzilla-daemon
2014-03-15  1:22 ` bugzilla-daemon
2014-03-17  7:02 ` bugzilla-daemon
2014-03-22  0:08 ` bugzilla-daemon
2014-03-29 14:28 ` bugzilla-daemon
2014-03-29 20:44 ` bugzilla-daemon [this message]
2014-03-31  3:45 ` bugzilla-daemon
2014-04-06 13:45 ` bugzilla-daemon
2014-04-09  6:35 ` bugzilla-daemon
2014-04-10  6:42 ` bugzilla-daemon
2014-10-29 11:37 ` 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-74868-502-0imuftvrQv@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.