Finished splitting the uber-deck into multiples of 16.
The triplehead2go drivers and firmware are up to date, but for this test that was unplugged so just using the internal nvidia gfx (which is up to date for drivers).
Select all clips in a deck and set to play random clip next.
Select another deck (or sometimes not).
Definitely repeatable but a bit random as to when.
This is on the laptop.
There is also definitely something quirky going on with the whole switching of decks. If I repeatedly switch between 'fully-loaded' (16cols, 5 layers) decks and watch the process memory usage with the sysinternals process explorer, there's a definite sawtooth trend upwards. So what starts with a memory usage of ~250Mb, grows in a couple of minutes of switching decks to 300Mb.
Personally, this suggests that whatever method is being used to hold individual decks in memory would be better changed to hold all of them at once to make the switching process smoother and not having the app eventually run out of memory
With it crashing again, I checked the Windows Event Log/Action Centre to see if it would tell me anything useful. What I got out of it is here (as apparently I can't add txt attachments!):http://www.evernote.com/shard/s32/sh/af ... 95495d77d6
It mentions about "cross-thread" something or other, which sounds relevant. If the app is producing a race condition between two threads, then something has to give
Anyone know an equivalent of strace for windows??