I've posted numerous console output, WoW crash and debugger logs...
How can you say this?!
I've already read over what to do and I've even prepared my own detailed templates for each machine I test on. What a rotten way to treat someone who is trying to help.
It crashes when I'm in a large area. My first guess would be that it might be an issue with the game drawing in scenery from the horizon. The crashes never seem to happen indoors or while in Warsong Gulch (a rather small pseudo-zone dedicated to one-time player vs. player battles).
On 10/31/06, Wine Bugs wine-bugs@winehq.org wrote:
http://bugs.winehq.org/show_bug.cgi?id=6505
------- Additional Comments From the3dfxdude@gmail.com 2006-31-10 12:41
Not abandoned, but kind of useless.
You really ought to determine whether this is caused by the wined3d backend. To me it looks like so. If that is the case, we know where to look. It could also be a sound bug or a thread priority bug. But this is what it appears like. Not enough information is given.
The idea of "random crashes" is really difficult to approach. Like describing two bugs in one report, reporting more than one crash at a time is the same thing. We can't really properly address both. Just focus on one and try to reproduce it, then dig out the information we need, and then we can clean up the description of the bug. This bug could be for example: "WoW crash after character selection screen" with component of wined3d, but I can't make that change because I don't know.
You might want to look here for more debugging techniques. (The first three sections) http://www.winehq.com/site/docs/winedev-guide/index
-- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You reported the bug, or are watching the reporter.