On Sat, Jan 1, 2011 at 10:00 PM, wrote:
> Happy New Year!
>
> i notice, that since 1.3 i get quite offten locking issue. It looks
> like, that last OK version was 1.2-rc7. This problem happens in
> Bioshock on load/save, but i noticed that other users have same
> problem with games on the same ga
On Sun, Jan 2, 2011 at 7:36 PM, Henri Verbeet wrote:
> On 2 January 2011 17:43, wrote:
>> The truth is, that wine outputs the first line ("...wait timed out
>> in thread 001c, blocked by 0041...") only once and after that only
>> the 2nd line repeats every 60sec ("...wait timed out in thread 004
On 2 January 2011 17:43, wrote:
> The truth is, that wine outputs the first line ("...wait timed out
> in thread 001c, blocked by 0041...") only once and after that only
> the 2nd line repeats every 60sec ("...wait timed out in thread 0045,
> blocked by 0044..."). Don't know if that's normal in t
On 2 January 2011 13:59, wrote:
> err:ntdll:RtlpWaitForCriticalSection section 0x7de77580
> "x11drv_main.c: X11DRV_CritSection" wait timed out in thread 001c,
> blocked by 0041, retrying (60 sec)
>
...
> Backtracing for thread 001c in process 001b (C:\Program Files\2K
> Games\BioShock\Builds\Rele
On 1/1/11 7:10 PM, Dan Kegel wrote:
Sometimes it helps to run winedbg from another window
and get the stacks of all running processes with the command
bt all
With luck, you can then see which two code paths are
competing for the lock.
Dan:
I've also been getting random 'locks' and this is o
Sometimes it helps to run winedbg from another window
and get the stacks of all running processes with the command
bt all
With luck, you can then see which two code paths are
competing for the lock.
