http://bugs.winehq.org/show_bug.cgi?id=25206
--- Comment #72 from Janne Hakonen joyer83@live.fi 2011-01-26 18:11:25 CST ---
With the +relay option im getting a timeout while the char is loading. The messages, typed to console need too mutch time, the program executes too slow. I piped that overhelming message salad to a file, bigger then 1GB. Now i havnt made it yet, to copy some pages before and after the crash because the file is so damn huge, im still working on that.
Oh yeah, just remembered that I have been using the +relay mainly with testing of AwesomiumGL, but I tried it now to see what happens. I was able to log in, open the browser and then log off properly (client was kinda [very] sluggish though). Log file was something like 650MB, huge that too, but not as huge as yours.
Try logging a toon without much of prefs data, in backyard, or someplace that is small and void of other players and monsters / npcs, maybe that would help.
If that's not enough, you could use some kind of faster storage device for the log file, maybe a ram disk, like: http://en.wikipedia.org/wiki/Tmpfs
I was not able to bind any debugging to the AwesomiumProcess.exe, how can i do that ?
See http://wiki.winehq.org/UsefulRegistryKeys, look for AeDebug -key, value is "winedbg --auto %ld %ld", remove the --auto part so that it says "winedbg %ld %ld", now the debugger stay open when the crash happens.
Do you use your exception solution in your RtlCaptureStackackTrace ? Or do you also just return 0; ?
I use the exception solution.
Ill make some futher tests with AwesomiumGL
Great, lets hope that the crash comes with that one too. :)