(In reply to Pierre-Eric Pelloux-Prayer from comment #19)
> (In reply to Marko Popovic from comment #17)
> > (In reply to Pierre-Eric Pelloux-Prayer from comment #15)
> > > (In reply to Marko Popovic from comment #14)
> > > >=20
> > > > Yes, always happens at the same place with Citra emulat=
or
> > >=20
> > > Could you capture a trace of the problem (using Apitrace or =
Renderdoc)?
> > >=20
> > > This would be very helpful to fix it.
> >=20
> > I added reproduced Citra crash recorded by using command:
> > apitrace trace ./citra-qt
> >=20
> > I hope this is correct, if you need anything else or done differe=
ntly please
> > just let me know!
>=20
> Thanks for the trace!
>=20
> Replaying the trace a few times is enough to reliably to reproduce the=
 hang.
>=20
> Using AMD_DEBUG=3Dnongg seems to prevent it so it could be a temporary
> workaround until a proper fix is found.
> Could you confirm this on your system?
>=20
>=20
> >=20
> > I am adding Rocket League crash output from apitrace.
>=20
> This trace file is very small (only one frame) and doesn't hang here.<=
/span >

Okay I just got another random hang on the desktop. even with the environme=
nt
variable turned on the whole time. Unfortunately it seems to be very hardly
tracable seems to be very random :( Seems that Citra hang is unrelated to t=
his
bug after all, it's a completely different bug. It's good that we discovered
another (citra-related) bug on the way but probably we can't mark that
workaround to solve anything because hangs still randomly occur on the desk=
top.