﻿<?xml version="1.0" encoding="utf-8"?><rss version="2.0"><channel><title>Ayende @ Rahien</title><link>http://ayende.com</link><description>Ayende @ Rahien</description><copyright>Copyright (C) Ayende Rahien  2004 - 2021 (c) 2026</copyright><ttl>60</ttl><item><title>C.J. Anderson commented on Challenge: Find the bug fix</title><description>oops.  someone got a correct answer in before I posted.  mea culpa.
</description><link>http://ayende.com/3449/challenge-find-the-bug-fix#comment8</link><guid>http://ayende.com/3449/challenge-find-the-bug-fix#comment8</guid><pubDate>Sun, 27 Jul 2008 01:35:22 GMT</pubDate></item><item><title>C.J. Anderson commented on Challenge: Find the bug fix</title><description>Very subtle.
  
  
The WaitHandle returned by IAsyncResult from the async write only "needs" to live until EndWrite is called.  Calling WaitAll can potentially throw an ObjectDisposedException if the handle is closed.
  
  
The calling set on the manually created handle does not release the handle for GC.
  
  
</description><link>http://ayende.com/3449/challenge-find-the-bug-fix#comment7</link><guid>http://ayende.com/3449/challenge-find-the-bug-fix#comment7</guid><pubDate>Sun, 27 Jul 2008 01:20:21 GMT</pubDate></item><item><title>Ayende Rahien commented on Challenge: Find the bug fix</title><description>Thomas,
  
Exactly.
  
But to make matters worse, it will _only_ happen in async mode!
</description><link>http://ayende.com/3449/challenge-find-the-bug-fix#comment6</link><guid>http://ayende.com/3449/challenge-find-the-bug-fix#comment6</guid><pubDate>Sun, 27 Jul 2008 01:13:29 GMT</pubDate></item><item><title>Thomas Krause commented on Challenge: Find the bug fix</title><description>stream.EndWrite() probably disposes the WaitHandle which causes WaitAll to fail.
</description><link>http://ayende.com/3449/challenge-find-the-bug-fix#comment5</link><guid>http://ayende.com/3449/challenge-find-the-bug-fix#comment5</guid><pubDate>Sun, 27 Jul 2008 00:23:02 GMT</pubDate></item><item><title>Ayende Rahien commented on Challenge: Find the bug fix</title><description>There is relation to ordering, but not in the way you are thinking about it
</description><link>http://ayende.com/3449/challenge-find-the-bug-fix#comment4</link><guid>http://ayende.com/3449/challenge-find-the-bug-fix#comment4</guid><pubDate>Sat, 26 Jul 2008 21:17:14 GMT</pubDate></item><item><title>Scott MacLellan commented on Challenge: Find the bug fix</title><description>Is it because of the order in which their event fires? For example, it will fire prior to the end actually occuring. It could also be that their reset event is configured differently than the one you are making, i.e. maybe their reset event is actually and AutoResentEvent.
</description><link>http://ayende.com/3449/challenge-find-the-bug-fix#comment3</link><guid>http://ayende.com/3449/challenge-find-the-bug-fix#comment3</guid><pubDate>Sat, 26 Jul 2008 21:14:12 GMT</pubDate></item><item><title>Ayende Rahien commented on Challenge: Find the bug fix</title><description>No, that is not an issue, they will simply execute in batches of 25
</description><link>http://ayende.com/3449/challenge-find-the-bug-fix#comment2</link><guid>http://ayende.com/3449/challenge-find-the-bug-fix#comment2</guid><pubDate>Sat, 26 Jul 2008 20:18:55 GMT</pubDate></item><item><title>Jo&amp;#227;o Bragan&amp;#231;a commented on Challenge: Find the bug fix</title><description>Is it because there are not enough ThreadPool threads (i think it defaults to 25 per cpu)?
</description><link>http://ayende.com/3449/challenge-find-the-bug-fix#comment1</link><guid>http://ayende.com/3449/challenge-find-the-bug-fix#comment1</guid><pubDate>Sat, 26 Jul 2008 20:16:11 GMT</pubDate></item></channel></rss>