Comment=
# 6
on bug 97174<=
/a>
from blackh=
eart_pro@yahoo.com
The conclusion I'm coming to is it's almost certainly some kin=
d of conflict
with Steam; particularly when launching the game through Steam itself. AAC =
is
DRM free, it doesn't need Steam to run. When I run the game without Steam, I
don't get any hangs at all. That's probably why I can't produce the hang wh=
en
running the command mentioned in com=
ment 3. Using apitrace with that command, I
don't believe it launches the game with the full Steam environment. Steam
doesn't appear to be running in the background and I can't shift+tab to get=
the
overlay. I can't properly record the hang without Steam present, but I'm not
sure how (or if i even can,) use apitrace + ACC with full Steam running as =
if
launched through the client. This also applies to GALLIUM_DDEBUG=3D1000 as =
well.
No hangs and it doesn't produce any files (they're supposed to appear in
/ddebug_dumps/ in the home folder, correct?)
(In reply to Daniel Scharrer from c=
omment #4)
> Does the game only temporarily freeze and then c=
ontinue, does it freeze permanently or does the whole system lock up?
Permanent. Only the game freezes. I can't even kill it when it does freeze,
I've tried everything. Strange that you aren't getting it. Are you using Me=
sa
12? That's the key here, Mesa 11 series doesn't suffer from this bug at all=
.=20
> you can use the following command to see where i=
t is stuck (you may need to install gdb first):
>gdb --pid `pidof cactus.x86_64` --batch -ex 'info=
threads' -ex 'thread apply all bt'
gdb is installed by default in Ubuntu 16.04, but seems I can't get this com=
mand
to work.