I would very much like to describe this error, but I have no idea what to tell you, and I realise it's not something I can reproduce very easily.
After fiddling a lot with breakpoints and the monitor, the machine looks like it's hung. (This is one of the times I REALLY would like to have the ability to have a breakout window showing the CPU activity)
When resetting the machine , I get the top part in the background colour (light green in my case) and the lower and the lower in light blue (normal background colour). I use the Action Replay 5.1 FairLight edition (https://csdb.dk/release/?id=137837) - hence the colours. And there it sits looking like a bad replica of the Ukrainian flag. Even if I run in warpmode it just hangs there and nothing moves. Until I press Alh+H for entering the monitor. Then the screen updates.
I tried going back to fiddle with my project more. Then I ran into the same thing also inside the project. Program looked totally frozen. Entering the monitor, screen refreshed and everything looked proper again.
For a second I thought it could be the binary remote remote monitor, but that it's marked as off.
No idea what this bug report is about - if you can break into the monitor, what about using chis to see what its doing?
Sorry for late feedback on this.
In summary; in warp mode, it seems that screen updates stops happening for some reason under some conditions. Emulation runs fine - it's just the screen updates that stops from happening.
This issue is still there in current trunk build, and it's there on both my desktop and my laptop. I do believe the gfx cards are totally different on the two, so it has to be with VICE itself, even if one suspect could have be the gfx driver. (Nvidia in the laptop - ATI in the desktop). For some reason, the reset process seemed to be prone to trigger it, but it happens every now and then.
Disabling warp it goes back to normal. As per the above, entering the monitor also seemingly kickstarted the screen refresh.
And I have found no way to reproduce it - it just happens every now and then. I'd say more often when I have run emulation for a longer period of time, but also not at all consistently so.
So my original heading is misleading - should rather be "Screen refresh stops"
I think I saw this too, once. I have no idea how to reproduce it: I was basically testing some incremental changes, and I ran pretty much the same thing on VICE every time, but it happened only once.
I have also seen this sometimes, clearly related to Warpmode, unrelated to Monitor
I believe this is fixed now, please let me know if otherwise.