Think I can do better than send you a file - I have concluded VP does not like large jpg's
Have had a play - and jpgs that work are around 600KB, and the ones that upset VP are around 6,000KB
The large ones are straight from my camera, and the smaller ones went through an image editor, and I guess it might have been my decision to go for 1920x1080 and consequently ending up with a smaller file size.
I have to add that VP went quite horribly wrong in that some of my experiments did not just fail to render (other than black) but actually corrupted the resultant file in strange ways. In one experiment I had 5 pics which were respectively pass/fail/pass/fail/fail and so I was expecting image/black/image/black/black, but actually got the first image correct, then 2 blacks, then a repeat of the 1st image again. I conclude the 'large' jpgs were perhaps overwriting VP internal storage with resultant chaos.
I provide no documentation of this final chaos as the solution is simple, reprocess the jpgs to a smaller file size. But that said, if you would still like one of my huge jpgs just ask.
It would be nice to know what the critical size is (to help us live with the problem until a fix is released) and that the fix would be to cure the problem so that large jpg's are not a problem (some users may want to use hi-res jpg's to be able to zoom in sections without image degration).
PS I have only seen this chaos using 'scale' effect, and a few others I have tried seem ok, so 'scale' seems vulnerable. There may be others but my investigations are definitely not exhaustive by any means. I would hope your tech team will fairly quickly find the suspect code, and effect a cure which will probably be universal. Only affected the render process, everything from inside VP looked as expected.