Hi Banacek,
GroovyMAME by default updates the screen on a separate thread of execution. The synchronization is very delicate and it's a terrible idea to mess with it from an external application because that can easily induce a dead-lock. Disabling -multithreading will revert this behaviour to MAME's standard so it fix this problem.