http://bugs.winehq.org/show_bug.cgi?id=31442
--- Comment #19 from voidcastr voidcastr@gmail.com 2012-10-01 15:02:39 CDT --- You mean a backtrace of the actual crash? That's the problem: The application simply freezes wihout any further output.
Nevertheless, http://bugs.winehq.org/attachment.cgi?id=41903 is a log from the startup to the crash. It was created with wine Gw2.exe &> log.txt using 1.5.14.
I don't know which warn or trace channels to activate... tried a few, but in any case the output was either totally spammy and did't even alter or stop after the freeze, or nothing interesting gets logged (especially not in the moment the application freezes).
Some more notes on what happens when the game freezes: - the process' CPU usage instantly drops from ~148% to 4% - background music is still playing -- however, sounds are not "live" anymore (those caused by other players next to my character cannot be heared) - input is dead, as expected
However, I just found that focussing a text input field for the FIRST time (either when trying to chat ingame or when prompted to enter the name for a new character) causes these two log lines when running the game with the -dx9single argument:
fixme:imm:ImmGetOpenStatus (0x396e55c0): semi-stub fixme:imm:ImmReleaseContext (0x80064, 0x396e55c0): stub
Without the -dx9single flag the application crashes before the above gets logged. However, since these lines can only be observed when running the application with its -dx9single flag, I'm not sure if the lines are present due to the very usage of the flag or if the fact that they are missing when omitting the flag is actually a symptom of the crash.