wine users - Jun 2009 - Wine debug trace log makes things better?

I was running Riven with the command for a debug trace log because I wanted to
file a bug report. Normally Riven freezes after the end of the intro video and
also freezes fairly often after other videos and transition effects.
But I found that when I ran Riven with the trace log command it didn't
freeze at all, is there a reason for this?

Should I still submit the trace log? I assume that as it didn't freeze the
debug trace log wouldn't show anything.

The command I used:
WINEDEBUG=+relay,+seh,+tid wine Riven.exe &> ./output.txt

Ezekiel000 wrote:
> But I found that when I ran Riven with the trace log command it didn't
freeze at all, is there a reason for this?
Yes, numerous reasons such as race conditions get "fixed", some memory
corruptions are avoided due to extra "padding", number of timing
issues (not covered under race conditions) get "resolved".

Lots of these issues are on Wine side, but some are hidden features of very game
you trying to run.

Ah right interesting. Well I found that it does freeze eventually but it takes a
while and the trace log it normally >10Gb. Is there a limit to the size of a
trace log when submiting bugs?