From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 62967] Game Dungeon Defenders crash my whole system.
Date: Mon, 01 Apr 2013 15:20:56 +0000 [thread overview]
Message-ID: <bug-62967-502-inCP3fLkEH@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-62967-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 1015 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=62967
--- Comment #2 from Thomas Lindroth <thomas.lindroth@gmail.com> ---
There is an upstream bug about this problem here.
https://bugzilla.icculus.org/show_bug.cgi?id=5895
Seems like it runs fine on the closed drivers.
The game freeze for several seconds during the intro as the game does about
6000 calls to glCompileShader. Here is an apitrace of the intro.
https://dl.dropbox.com/s/ynibt38hhdlyu1r/DungeonDefenders-x86.trace.bz2
glretrace will segfault while playing it back in r600_dri.so during a call to
glDrawRangeElements. I couldn't get a backtrace because of corrupt stack.
Playing back the trace with softpipe will not segfault but it will have the
drawing errors.
Mesa-9.1 and git from a few days ago both got the problem. 3.8.4 kernel,
juniper hardware.
Option "ColorTiling" "true"
Option "ColorTiling2D" "true"
Option "SwapbuffersWait" "false"
Option "EnablePageFlip" "true"
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2019 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
next prev parent reply other threads:[~2013-04-01 15:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-31 16:45 [Bug 62967] New: Game Dungeon Defenders crash my whole system bugzilla-daemon
2013-04-01 12:49 ` [Bug 62967] " bugzilla-daemon
2013-04-01 15:20 ` bugzilla-daemon [this message]
2013-05-20 13:17 ` bugzilla-daemon
2016-07-15 4:01 ` 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-62967-502-inCP3fLkEH@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