http://bugs.winehq.org/show_bug.cgi?id=11706
--- Comment #13 from Roman m01brv@mail.ru 2010-11-17 03:45:41 CST --- Created an attachment (id=31988) --> (http://bugs.winehq.org/attachment.cgi?id=31988) another backtrace + thread info in the crash on startup
I could catch another backtrace of the crash leading to the freeze on startup, different from the first one here. I realized it is not a freeze actually, the application just awaits when the user closes a crash dialog behind the main warcraft window. I could not just to alt-tab to this crash dialog, it always remains behind the main window, and could be seen only *during* alt-tabbing with desktop compositing effects enabled. This crash does not occure on each start, the probability to get it is around 10-50%, depending on conditions (e.g. whether or not the KWin effects are enabled, whether or not the game is run via winedbg, and on winedbg registry keys).
This backtrace ends in i965_dri.so, i.e. this bug may be indeed related to the intel 3D driver. However, please note there are two subsequent calls to wine_glClear (even with different parameter), which seems never call itself recursively, according to the wine sources. This looks very strange.
I use KDE 4.4.2, Ubuntu Lucid, wine 1.3.4. I remember that the same issue existed with many previous wine versions and Ubuntu releases, so it is pretty aged.