Opened 10 years ago

Last modified 2 years ago

#1038 new feature request

Exception handling should be improved, no exception should crash the optimizer

Reported by: abeham Owned by: swagner
Priority: medium Milestone: HeuristicLab 4.0
Component: General Version: 4.0
Keywords: Cc:


There should be almost no errors that crash the Optimizer as a whole. Maybe a solution along attaching an event handler to Application.ThreadException which a mainform window should provide to handle exceptions. I'm not too firm with exception handling in C# though. Found this to possibly be useful:

Finally there should be possibilities to issue warnings and errors (I think there should be a distinction) to the GUI.

We should also think about properly integrating a logging library and include a build configuration that makes use of this library. So that one can assemble a log-build of HL to give to someone who's having troubles which are perhaps difficult to find out otherwise.

Change History (4)

comment:1 Changed 10 years ago by swagner

  • Summary changed from Improve Error Handling in HeuristicLab to Improve error handling in HeuristicLab

comment:2 Changed 9 years ago by swagner

  • Milestone set to Iteration 4

comment:3 Changed 6 years ago by gkronber

  • Milestone changed from HeuristicLab 3.3.x Backlog to HeuristicLab 4.0.x Backlog
  • Summary changed from Improve error handling in HeuristicLab to Exception handling should be improved, no exception should crash the optimizer
  • Version changed from 3.4 to 4.0

comment:4 Changed 2 years ago by pfleck

The ErrorDialog/ErrorHandling should explicitly handle AggregateExceptions by unwrapping/flattening the InnerExceptions. Currently, only a single InnerException (only the first one in case of an AggregateException) is displayed.

Note: See TracTickets for help on using tickets.