Re: multiple threads writing to WebBrowser, getting deadlocked
- From: "Zytan" <zytanlithium@xxxxxxxxx>
- Date: 3 Apr 2007 12:10:16 -0700
Hmm. You've still got a potential deadlock, unfortunately.
Yes, I knew that... I should have been accurate and said that if you
click it just at the right time, you have a chance to create the
deadlock, since the same conditions still exist. But, the likelihood
is 1 in a billion.
I realy didn't mean this was a solution. I meant to show how code
that you would think is broken appears to run fine. It's still
broken. And this really threw me off.
Using BeginInvoke is certainly a reasonable way of avoiding this,
although I'd avoid calling Thread.Join in the UI thread too.
Yes, I choose both (call Control.BeginInvoke, and to not call
Thread.Join)
Zytan
.
- Follow-Ups:
- Re: multiple threads writing to WebBrowser, getting deadlocked
- From: Ravichandran J . V .
- Re: multiple threads writing to WebBrowser, getting deadlocked
- References:
- multiple threads writing to WebBrowser, getting deadlocked
- From: Zytan
- Re: multiple threads writing to WebBrowser, getting deadlocked
- From: Zytan
- Re: multiple threads writing to WebBrowser, getting deadlocked
- From: Zytan
- Re: multiple threads writing to WebBrowser, getting deadlocked
- From: Jon Skeet [C# MVP]
- multiple threads writing to WebBrowser, getting deadlocked
- Prev by Date: Re: Total confused and need help with small encryption and decryption methods
- Next by Date: Re: global settings question
- Previous by thread: Re: multiple threads writing to WebBrowser, getting deadlocked
- Next by thread: Re: multiple threads writing to WebBrowser, getting deadlocked
- Index(es):
Relevant Pages
|