Pause is not Pausing

There was a major rewrite in 2.0.3.6 to add concurrency in hopes of increasing performance, that might have caused the changes I cited earlier, as lots of code got moved, and possibly some got left behind…

I think there are reports in the forum of issues from pause or stop, so maybe it also avoided some bugs. You probably won’t find active forum participants who were close enough to the plans to give you details.

From a forum point of view, it might not be a Feature but it’s not exactly Support. It ought to be in issues, which can track issues better. Perhaps it already is. Maybe someone can see if anyone has good ideas.