Opened 9 years ago
Closed 7 years ago
#2556 closed defect (duplicate)
OptimizerView must resync with optimizer content
| Reported by: | abeham | Owned by: | abeham |
|---|---|---|---|
| Priority: | medium | Milestone: | |
| Component: | Optimization.Views | Version: | 3.3.13 |
| Keywords: | Cc: |
Description
In rare cases it may happen that the optimizer is in a different state than the view showing it. The optimizer e.g. goes into state stopped while the view still displays it as running. Any attempt to pause or stop the optimizer results in an exception. Unfortunately one has to take the whole AppDomain down, because closing the view also attempts to stop the optimizer which results in an exception and thus unsuccessful closing.
I don't know exactly why the content and view become out of sync, but I have seen this bug several times.
Change History (4)
comment:1 Changed 8 years ago by mkommend
comment:2 Changed 8 years ago by mkommend
- Milestone changed from HeuristicLab 3.3.14 to HeuristicLab 3.3.15
comment:3 Changed 7 years ago by abeham
- Owner set to abeham
- Status changed from new to accepted
comment:4 Changed 7 years ago by abeham
- Milestone HeuristicLab 3.3.15 deleted
- Resolution set to duplicate
- Status changed from accepted to closed
The case that mkommend mentioned has been addressed in ticket #2711.
Note: See
TracTickets for help on using
tickets.
A reason for this behavior might be an invisible exception during the object graph traversal when the algorithm stops.