OptimizerView must resync with optimizer content
|Reported by:||abeham||Owned by:|
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.