Comment 9 for bug 1067328

OK; procedure to replicate this UI lock-up is now very easy and I think proves it is not related to input file format:

Start Openshot from command line using

openshot test_file &

IMMEDIATELY press 'Preview play' button (even though the clip thumbnail has not been dropped onto the timeline).

The 'slider button' jumps almost immediately to right hand end of travel; depending on whether mouse is still hovering over the Play/Pause button you may see the Play/Pause legend flash briefly.

MOST of the time, from this point on, 'Desktop / UI' lock up is as described earlier; on one occasion so far I have been able to re-wind using the 'seek to start' button a couple of times, but then produced the lock-up as described by dropping the clip on the timeline, and shortenning the clip using the Resize tool.

Using Ctrl-Alt-F2 to open a root console window, you can see about 8% of CPU is used, AND I think a gradually increasing amount of memory (will leave it running a while to check).