The following comments are owned by whoever posted them. WineHQ is not responsible for what they say.
RE: Random Crashing as of the March 27 Version Update
by Chiitoo on Thursday March 29th 2012, 15:42
Thank you, and thank you jacob wilson as well!
It is certainly reassuring to get a confirmation on this, and will try to look into it as much as I can, as soon as I can, but I have done only so little debugging yet with Wine, that it may well take until someone more experienced will do it.
Since I had the client crash at the title screen, I let it sit there, sometimes going into the character selection screen and back, and it would eventually crash when about half-done with loading the title. I don't think it has yet crashed while just sitting there, but instead, only when I go back to it from the character selection...
I also noticed the
error will completely flood the terminal during certain times (as I remembered, I have been seeing it before, but did not think about it much). For an example, when the 'camera is flying' at 'Aht Urhgan Whitegate' or 'Al Zahbi' at nighttime, the flood is there. It will likely do it in the 'Wings of the Goddess' areas as well, because those, similar to Whitegate, inflict a staggering performance drop (another indication to a crippled movement is CPU usage going hiiigh-er). It is most noticeable if one is running two clients at the same time, and both of the characters are in one of those areas, same or different. The 'lag' also more or less vanishes if one turns the 'camera' to look up, or down. Don't know if the "err" will vanish then too. Probably not completely, but the flood might slow down, I'd imagine.
Need to try and look into it more when time permits.
Other messages that are also present at times (not in a floody manner at any times):
I don't think these are related to this major issue, though. I just figured I'd document them here either way. The first usually comes in several lines when, for example, the title screen loads a new area. Sometimes it does more or less flood a terminal, but it is not constant, and stops very soon.
It's borderline hilarious that when they fix something, they seem to break something. Most recent (excluding this as it does not seem to affect the client running on Windows or at least I have not seen any reports, I haven't tried myself) is the character-movement issue (though more than about fixing something, this was about adding new methods for control). I even reported that issue on the test-server board a MONTH before the update went live, and unsurprisingly, they either didn't even get the report translated at all, or they just didn't bother with it...
But yeah, as I mentioned, it might take me a while to get even a bug-report done, so, if you are impatient, consider doing it yourself and get the ball rolling! ^^;
A-ny-ways, enough blabbering!
Again, thanks for confirming that it is indeed not just me, which I was rather sure about, but it's always better to more than sure!