Exactly, that's the workaround I described in the thread opening.
I'm only posting here, because (a) if someone else runs into the same issue and doesn't know what happening. And (b) it would be great if the issue could be addressed by having Resolume remain responsive, maybe even with some indication what's happening.
