Re: How to find out locking problem

2011-01-03 Thread Austin English
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

Re: How to find out locking problem

2011-01-03 Thread Damjan Jovanovic
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

Re: How to find out locking problem

2011-01-02 Thread Henri Verbeet
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

How to find out locking problem

2011-01-02 Thread wylda
Hi Henri, thank you for analysis, it's first time when i'm trying to help with this kind of problem... > > From that backtrace, it doesn't look like 001c is > waiting for a critical section at all. > The truth is, that wine outputs the first line ("...wait timed out in thread 001c, blocked by

Re: How to find out locking problem

2011-01-02 Thread Henri Verbeet
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

How to find out locking problem

2011-01-02 Thread wylda
> ...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. Thanks for tip! Are the following traces from problematic threads useful or will i have to post all the thread traces? (Just repeat: happens

Re: How to find out locking problem

2011-01-01 Thread James McKenzie
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

re: How to find out locking problem

2011-01-01 Thread Dan Kegel
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.

How to find out locking problem

2011-01-01 Thread wylda
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 game engine. Could someone help me, what should i do i