Based on my current findings, this issue happens when displaying a static screen (no animation or movement) after removing an image and then display a new image object or after updating a text object. It’s a bit more complicated than that, but it’s much more likely to happen on static screens.
I believe I have a fix for this now, but I’ll have to run it through a gauntlet of tests tomorrow to make sure it works and doesn’t break anything else. If all goes well, we’ll make this fix available in a daily build by Monday (but hopefully sooner). Thanks for your patience.
