From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 106928] When starting a match Rocket League crashes on "Go"
Date: Thu, 28 Jun 2018 18:06:51 +0000 [thread overview]
Message-ID: <bug-106928-502-nVWHOssPdw@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-106928-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 1091 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=106928
--- Comment #7 from ubizjak@gmail.com ---
(In reply to Roland Scheidegger from comment #6)
> At a quick try I can't reproduce this on my HD 5750. Albeit I tried
> chromium, and probably not the same version.
> The replay doesn't assert neither, though I get lots of link errors due to
> usage of glProgramBinary it seems (also needed gl/glsl version overrides).
> Might need to disable ARB_get_program_binary when capturing?
> From the backtrace it sort of looks like trying to fold a alu3 op with only
> 2 sources but I've no idea really. I hope it's not compiler dependent
> (valgrind was of no use neither).
> Since this appears to be a regression, you could try to git bisect.
Please configure the build with:
CXXFLAGS="-Wp,-D_GLIBCXX_ASSERTIONS" ./autogen.sh
Rest assured that the assert will be triggered. I have tried with build of Mesa
18.0.5 (git-ca0037aaef). Just invoke firefox from command line and navigate to
Google Maps.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1979 bytes --]
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2018-06-28 18:06 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-15 12:21 [Bug 106928] When starting a match Rocket League crashes on "Go" bugzilla-daemon
2018-06-15 12:59 ` bugzilla-daemon
2018-06-22 16:26 ` bugzilla-daemon
2018-06-26 15:50 ` bugzilla-daemon
2018-06-26 16:27 ` bugzilla-daemon
2018-06-26 22:16 ` bugzilla-daemon
2018-06-27 0:38 ` bugzilla-daemon
2018-06-28 18:06 ` bugzilla-daemon [this message]
2018-06-28 18:30 ` bugzilla-daemon
2018-06-29 0:09 ` bugzilla-daemon
2018-06-29 2:57 ` bugzilla-daemon
2018-06-29 7:16 ` bugzilla-daemon
2018-06-29 15:09 ` bugzilla-daemon
2018-06-29 19:09 ` bugzilla-daemon
2018-06-29 20:11 ` bugzilla-daemon
2018-06-29 20:23 ` bugzilla-daemon
2018-06-29 20:45 ` bugzilla-daemon
2018-06-29 20:54 ` bugzilla-daemon
2018-07-04 7:50 ` bugzilla-daemon
2018-07-10 7:57 ` bugzilla-daemon
2018-07-10 8:15 ` bugzilla-daemon
2018-09-07 17:36 ` bugzilla-daemon
2018-09-07 18:28 ` 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-106928-502-nVWHOssPdw@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;
as well as URLs for NNTP newsgroup(s).