http://awalsh128.com/tags/multithreading/Recent content in Multithreading on Andrew WalshHugo -- gohugo.ioen-US© 2026 Andrew WalshSat, 25 Oct 2014 18:18:59 -0700http://awalsh128.com/wpf-and-data-multithreading-deadlocks/Wed, 21 Dec 2011 00:00:00 -0800http://awalsh128.com/wpf-and-data-multithreading-deadlocks/<h2 class="relative group">WPF &amp; Multithreading <div id="wpf--multithreading" class="anchor"></div> <span class="absolute top-0 w-6 transition-opacity opacity-0 -start-6 not-prose group-hover:opacity-100 select-none"> <a class="text-primary-300 dark:text-neutral-700 !no-underline" href="#wpf--multithreading" aria-label="Anchor">#</a> </span> </h2> <p>In designing applications, it may be advantageous to run data processing methods on a separate thread from the UI. This allows greater responsiveness in the application and takes advantage of concurrent computation.</p>http://awalsh128.com/reentrant-lock-acquires-in-clr/Fri, 29 Jul 2011 00:00:00 -0700http://awalsh128.com/reentrant-lock-acquires-in-clr/<p>I always like when a post gets to the point (especially after searching in Google). In short, <em><a href="http://msdn.microsoft.com/en-us/library/ms741870.aspx" target="_blank" rel="noreferrer">if you perform an operation that waits to acquire a lock, the thread doesn't actually stop</a></em>.<br> <br> In concrete terms of .NET coding, if you call the <a href="http://msdn.microsoft.com/en-us/library/system.threading.waithandle.waitone.aspx" target="_blank" rel="noreferrer">WaitOne</a> method on a thread, it may still process events that the CLR deems &quot;high priority&quot;. This can be a big problem if the event handlers go into the critical region you are trying to protect.<br> \</p>