From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 97852] Unreal Engine corrupted preview viewport
Date: Sun, 30 Oct 2016 17:01:24 +0000 [thread overview]
Message-ID: <bug-97852-502-s8IMHSdh9t@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-97852-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 824 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=97852
--- Comment #5 from Markus <mw@graph-ix.net> ---
(In reply to Nicolai Hähnle from comment #3)
> Use this tool: https://github.com/apitrace/apitrace to record a session that
> shows the problem. Once installed, you basically just run `apitrace trace
> <program under trace>`. The documentation linked to in the readme is
> generally pretty good.
Hi Nicolai, an API trace is now attached. The trace was created with Mesa
version 13.1~git161022230600.7b7eb71~x~padoka0 where the issue is still
present.
The major part of the trace probably consists of the editor starting up, so the
issue itself should only be captured in the seconds prior to the editor
starting to shut down.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1713 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:[~2016-10-30 17:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-18 19:39 [Bug 97852] Unreal Engine corrupted preview viewport bugzilla-daemon
2016-09-28 12:00 ` bugzilla-daemon
2016-10-09 15:59 ` bugzilla-daemon
2016-10-09 18:31 ` bugzilla-daemon
2016-10-30 16:57 ` bugzilla-daemon
2016-10-30 17:01 ` bugzilla-daemon [this message]
2016-10-31 6:24 ` 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-97852-502-s8IMHSdh9t@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