Catching unhandled exception on separate threads

by

@Ani have already answered your question. Although I don’t agree that unhandled exceptions in threads should terminate applications. Using threads usually means that you have some kind of server application. Bringing it down could result in a lot of angry users.

I’ve written a small piece about proper exception handling: https://coderr.io/exception-handling

You should always catch exceptions for threads. I usually use the following pattern:

  void ThreadMethod(object state)
  {
      try
      {
          ActualWorkerMethod();
      }
      catch (Exception err)
      {
          _logger.Error("Unhandled exception in thread.", err);
      }
  }

  void ActualWorkerMethod()
  {
      // do something clever
  }

It’s a whole lot easier to find thread methods that doesn’t handle exceptions properly by moving the logic into a seperate method and just keep the try/catch block in the thread method.

More Related Contents:

  1. How to keep running a program if an exception occurs? [duplicate]
  2. VS2010 does not show unhandled exception message in a WinForms Application on a 64-bit version of Windows
  3. Is there a difference between “throw” and “throw ex”?
  4. WPF global exception handler [duplicate]
  5. Best practices for catching and re-throwing .NET exceptions
  6. Catch an exception thrown by an async void method
  7. Globally catch exceptions in a WPF application?
  8. Get connection string from App.config
  9. UnauthorizedAccessException cannot resolve Directory.GetFiles failure [duplicate]
  10. catch exception that is thrown in different thread
  11. Is it abusive to use IDisposable and “using” as a means for getting “scoped behavior” for exception safety?
  12. .NET Global exception handler in console application
  13. Is there a reason Image.FromFile throws an OutOfMemoryException for an invalid image format?
  14. Why use finally in C#?
  15. How to use ELMAH to manually log errors
  16. What’s the difference between Application.ThreadException and AppDomain.CurrentDomain.UnhandledException?
  17. Handling exceptions, is this a good way?
  18. File access error with FileSystemWatcher when multiple files are added to a directory
  19. The calling thread cannot access this object because a different thread owns it [duplicate]
  20. How can I catch a 404?
  21. Why is try {…} finally {…} good; try {…} catch{} bad?
  22. When to use try/catch blocks?
  23. Wrong line number on stack trace
  24. How to catch ALL exceptions/crashes in a .NET app [duplicate]
  25. Is this a bad practice to catch a non-specific exception such as System.Exception? Why?
  26. try catch finally question
  27. What is ApplicationException for in .NET?
  28. Show line number in exception handling
  29. Getting Cross-thread operation not valid [duplicate]
  30. How to log all thrown exceptions?

Leave a Comment