https://demozoo.org/productions/169 - http://ftp.amigascne.org/pub/amiga/Groups/L/Lemon/LEMON-Groovy.DMS
At 1:20 there should be a white line on the left side of this box in the middle as seen here http://www.youtube.com/watch?v=B2DT-n6p9c8&t=1m20s In vAmiga it's missing

The patient goes to X-ray... please hold on 馃樂.

As we can clearly see, the patient is suffering from a particularly severe form of "Copper" 馃. Copper activity (yellow) is all over the place.
Let's view it without the Copper...

In addition to hiding Copper DMA, I removed all sprite layers. The result is fascinating. The playfield only covers two third of the rectangle. The right part is covered partly by sprites. Between the sprites, there is still something to see, but there is no bitplane DMA going on. And there is no sprite DMA in these lines. This means that either the DMA debugger went crazy (unlikely) or the sprite and bitplane data registers are filled manually in this area. This would explain the heavy Copper load 馃.
How in the world shall I debug this? 馃檲
Might be worth looking at the DMA debugger in UAE to see how it differs?
I have an idea what this can be. It's possible with the copper to repeat sprites (example here https://codetapper.com/amiga/sprite-tricks/risky-woods) and as there are no bitplanes enabled maybe that is the case here.
I think this is the case where sprites can be horizontally visible 1 lores pixel before first possible visible bitplane pixel. Very annoying hardware feature to emulate..
But I think bitplanes are fully disabled in this case. Does that still happen then?
I think this is the case where sprites can be horizontally visible 1 lores pixel before first possible visible bitplane pixe
In theory, vAmiga should be able to handle this. There are special tests in Sprites/clip for this:
Fixed in v0.9.12 馃槑

fixed by 644af85 ?
I didn't verify which checkin actually fixed it (didn't run the demo for a while), but I share your guess. I think it was likely caused by the Line Blitter issue. BTW, this was a really stupid cut-and-paste style bug. I applied a pointer mask to a boolean instead of testing it for zero. I hope this piece of code didn't find it's way into the Arctic preservation project 馃檲.
haha :)