TimedLock class: helping find and avoid deadlocks in your multithreaded code

My blog has moved. You can view this post at the following address: http://www.osherove.com/blog/2005/4/8/timedlock-class-helping-find-and-avoid-deadlocks-in-your-mul.html
Published Friday, April 08, 2005 1:20 PM by RoyOsherove
Filed under:

Comments

Friday, April 08, 2005 2:09 PM by haacked@gmail.com (Haacked)

# Re: TimedLock class: helping find and avoid deadlocks in your multithreaded code

Hi Roy, actually, the version to use is http://haacked.com/archive/2004/10/13/1341.aspx. This one implements resolves the perf issue Ian noted with storing stack traces. It actually grabs the stack trace after the fact. A really ingenious solution proposed by one of Ian's readers that I implemented.
Friday, April 08, 2005 2:10 PM by Haacked (aka Phil Haack)

# re: TimedLock class: helping find and avoid deadlocks in your multithreaded code

Hi Roy,

Actually, the version to use is http://haacked.com/archive/2004/10/13/1341.aspx. This one resolves the perf issue Ian noted with storing stack traces in a hash table when you acquire a lock. It actually grabs the stack trace after the fact. A really ingenious solution proposed by one of Ian's readers that I went ahead and implemented.

Phil
Friday, April 08, 2005 7:10 PM by Roy Osherove

# re: TimedLock class: helping find and avoid deadlocks in your multithreaded code

Thanks Phil. I updated the links.
Monday, April 11, 2005 4:13 AM by federico

# re: TimedLock class: helping find and avoid deadlocks in your multithreaded code

Spring.NET (www.springframework.net) is trying to add several concurrency utilities (http://www.springframework.net/doc/reference/html/threading.html).

It also has an implementation of the same semantic (look for SyncHolder), just not timed.

However, I'd like to attract as much attention as possible to the Spring.NEt effort towards top quality, reusable, concurrency utilities.

Thanks,
Federico