9
« on: September 16, 2010, 08:10:42 AM »
Hi! Stability of the new beta 2.3.1009.08 is much better with wmv files!
I seem to see a problem when I have 2 instances open (I find it useful to have 2 instances open to make my workflow more efficient - while 1 instance is performing the trimming operation on clip A, I use the second instance to browse clip B and select which sections to keep). In this situation the instance that is trimming may freeze after reaching 99% complete for a particular tasks. I then see a Microdoft Visual C++ Runtime Library error window:
Runtime Error!
Program:D:\Program Files (x86)\S...
This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information.
For example, in the case i am looking at the trimmer task was going to process 16 tasks, but hung at task 1/16 (99% of current task, 6% of total).
However, in a previous occurence it completed 4 out of 17 tasks and hung on the 5th one.
In both occurences it hangs at 99% of the current task. The trimmed clip file is written to disk but not closed properly.
This has happened 4 times over the past day. In some cases the C++ Runtime Error window was not displayed - in this case the trimming process could be cancelled and the SolveigMM window closed, but the SMMVSplitter.exe *32 process was left hanging and had to be killed through Task Manager.
I have observed this with both wmv & mpg files. It does not happen the first time I start the second instance - usually both instances complete one or two clip processing sequences successfully before one of them freezes.
I have not observed this scenario with the previous stable version (2.2.1005.17).
Maybe you will be able to reproduce this in your lab?