The following ways to avoid "stuck" multithreading in C#: Avoid performing time-consuming operations on UI threads. Use Task and async/await to perform time-consuming operations asynchronously. Update the UI on the UI thread via Application.Current.Dispatcher.Invoke. Use CancellationToken to control task cancellation. Make rational use of thread pools to avoid excessive creation of threads. Pay attention to code readability and maintainability, making it easy to debug. Logs are recorded in each thread for easy debugging.

C# Multithreading: The Art of Elegantly Avoiding "Hard"

You must have had this experience: the program suddenly stops moving, the mouse pointer becomes an hourglass, and the world seems to be still... The concurrency ability brought by multi-threading programming is tempting, but if you are not careful, it may become a nightmare for your program, causing you to fall into the abyss of "stagnation". In this article, let’s talk about how to elegantly avoid this embarrassment in C#, so that your multi-threaded program can gallop like a wild horse without losing control.

First of all, you need to understand that the so-called "stuck" is usually not a problem with the thread itself, but the UI thread is blocked. Your program may have multiple hard-working threads, but if they are all waiting for the UI thread to process the results, once the UI thread is blocked, the entire program will be in a state of silence. Therefore, the key is to remove the burden on UI threads.

Let's review the basics first. C# provides Thread class and Task class for multi-thread programming. Task is based on ThreadPool , which is more convenient to manage and has higher resource utilization, so we mainly use it. In addition, the keywords async and await are powerful tools for asynchronous programming. They make the asynchronous code look as simple as synchronous code and are the key to avoid blocking UI threads.

Now, let's dive into the core: how to avoid UI thread blocking. The most common solution is to use BackgroundWorker , but it is a bit outdated, and it is now more recommended to use Task in combination with async/await . Take a look at this example:

 <code class="csharp">private async void Button_Click(object sender, RoutedEventArgs e) { // 禁用按鈕，防止重復(fù)點(diǎn)擊button1.IsEnabled = false; try { await Task.Run(() => { // 模擬耗時(shí)操作Thread.Sleep(5000); // 更新UI需要使用Dispatcher Application.Current.Dispatcher.Invoke(() => { label1.Content = "耗時(shí)操作完成!"; }); }); } catch (Exception ex) { // 處理異常Application.Current.Dispatcher.Invoke(() => { label1.Content = $"錯(cuò)誤: {ex.Message}"; }); } finally { // 啟用按鈕button1.IsEnabled = true; } }</code>

In this code, the time-consuming operations are placed in Task.Run and executed asynchronously. The key lies in Application.Current.Dispatcher.Invoke , which ensures that UI update operations are executed on the UI thread, avoiding conflicts. try-catch-finally block ensures the robustness of the program, and can be handled gracefully even if an exception occurs, and will not cause the program to crash.

To be more advanced, you can use CancellationToken to control task cancellation to avoid unnecessary resource waste. For example, if the user clicks the "Cancel" button, you can cancel the executing task through CancellationTokenSource .

Remember, don't perform time-consuming operations on UI threads! This is the golden rule of multi-threaded programming. Any operations that may block UI threads should be executed in a separate thread and then updated with Dispatcher or similar mechanism.

Finally, regarding performance optimization, try to avoid overuse of locks, as locks will reduce concurrent performance. Use thread pools reasonably to avoid creating too many threads. The readability and maintainability of the code are also very important. Clear code is easier to debug and maintain, reducing the possibility of "stagnation". A good habit is to log in every thread so that problems can be quickly located during debugging. Remember, elegant multi-threading programming requires you to have a deep understanding of concepts such as concurrency, asynchronousness, thread safety, etc. This requires accumulation of experience and continuous learning and practice.

The above is the detailed content of C# multi-threaded method to prevent jamming. For more information, please follow other related articles on the PHP Chinese website!