Hi, thanks for sharing this issue.

Does the issue appear for you at all if you keep the status indicator window closed?

Can you confirm whether you have any other 3rd party packages installed, and if so, whether temporarily removing them helps with the issue?

This issue seems contextually relevant, as it's another situation where we've had performance issues related to WM_RESIZE. I think there are some configurations that can cause the platform to spam this event and cause crashes and performance issues. The Status Indicator is perhaps susceptible to this because the logic it has inside the resize event is non-trivial (though not as bad as the Tests Window with a lot of trace output). In the reported case, the root problem seemed to be a DPI scaling glitch related to the scrollbar.

I'll warn you that problems of this nature are hard to fix, because I'm unlikely to find a way to reproduce them. It's basically a case of fix and hope. You'll notice that in the above thread, we got there in the end. Any further data you can share that might help to narrow down the problem would be a huge help.

Any info you can get me will help. Try keeping that indicator closed for a few days and let me know how it goes. If the problem doesn't reappear, then we can be certain that it's isolated to that component and I can try making some adjustments to it.

Thanks for confirming this. The Status Indicator Window is very old and is known to have performance issues when working with larger solutions with many tests. The central issue with it is that it relies on conducting simulations to determine the overall processing time/window, which is computationally extremely expensive.

I recommend avoiding the use of this window in your solution.

There's currently 3 good ways to get this info:
- The label at the top of the Tests Window reports the number tests in the queue. Just under this you'll see a coloured bar that indicates how many of the tests are passing or failing. The shade of these regions determines how many of these tests are from current (recently run) data or stale (out of date) data. When the bar has no darker regions, all tests are run.
- The NCrunch spinner in the corner of the IDE has a number of points that spin around the center text/number. Each of these represents an execution task. When nothing is spinning, the queue is clear.
- Hovering the cursor over the spinner gives detailed information including the same coloured bar from the Tests Window along with numbers on how many tasks and tests there are in each category.

My own experience was that when getting used to the above, I never missed the Status Indicator Window.