Resolume Forum

Hi All,
I have been having some serious problems with Arena. It keeps crashing with no apparent cause. Pretty much every hour of runnime it just stops working. I have tried updating my ram and running off a faster Hdd and this has not fixed the problem at all. I am running on a HP DV6 Laptop i5 2410 with 8gb of ram and a ATI 6770m on windows 7. My specs are more than high enough and I just cant seem to find the cause of the crashes....it just comes up with this program has stopped working...it cant be a resource problem as i have 8gb of ram. Any help with this problem with be greatly appreciated as I have had some serious crashes during some very important gigs (of which luckily i had an alternate video source).
Cheers
Nate
VJ Tesla

Sounds like a similar problem to I've been having, at the moment I'm citing compositions that were made pre 4.0.1 as everything "new" has been ok so far. No idea what the issue is....

viewtopic.php?f=12&t=9276#p35353

Cheers for the heads up indyLD


ok....soooo I have since upgraded my Hdd to a 120gb ssd with 500mb/s read/writte and upgraded my ram to 8gb as well as purchasing a laptop cooling pad. Everything seems to be working alot smoother now. I do feel like the ssd has made a maasive differnce.

However in saying that when I load one of my Large compilations...with about 10 layers My memory get used up quite quickly and after about 30mins I get a low memory warning in red in the bottom right of the arena screen. Now if i ttry and load any more clips into the projects or even just search through any folders in the folder view....the program crashes.

I am quite confused about this as i have just re-installed a clean system on and there are no background task running at all.....however the memory usage for resolume starts at about 3gb and just keeps slowly creeping up until it crashes.

Is their a max number of clips i should be using in each deck or the whole composition?
Is there any possibility in the future that resolume will beecome a 64bit program that can utilize more than 3.5gb ram?

The only fix to this i can see is if i remake all my compositions with alot less clips which is quite restrictive.

I had a very important gig at a festival the other week and it was very embasising to have to use a video switcher to swap to my backup laptop to run visuals at least 3 times in a 5 hour gig whilst i waited for arena to re-load on my main laptop.

Please help!!!!
Peace
Nate
(VJ Tesla)

The low memory warning is a good indication that Resolume is having trouble, and using less clips per deck would be a good idea.

Hoe many clips are you currently using?

I have also 8gig of Ram and never got such a message. Probably the crashes are related to this problem?? viewtopic.php?f=12&t=9236

And I thought it was just me!...
4.0.1 does seem to be crashing a bit more - the stablest version I've used was actually beta2...
I've also got quite a large composition, currrently one large deck, 5 layers, ~140 columns - because changing decks is still quite slow
One thing I discovered was that while Arena does run fine with the internal NVidia GFX, when I add on the Matrox Triplehead2go (so that I can have independently sized main/monitor outputs) it gets a little temperamental - although removing and reinstalling the drivers has helped a little. I left Arena running overnight last night with all clips sets to "randomly select next clip" set and it had crashed by morning /

I'm going to be trying to split up my massive composition into '16 columns per deck' over the next few days, partly to see if it helps with the app memory usage as discussed above and partly to use it with an OhmRGB.
Will let you know how I get on!

you can also try to update the firmware of your triplehead2go if not done yet....
should be done if new drivers are used i think!

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).
App crash!
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


update:
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??

Thanks for the error report and thorough testing! Are you using Flash content? Flash has to run on a priority thread, so it could potentially interfere with deck switching.

I recognized three different Versions of Crashes:

1. It crashes while switching the decks and reload all assigned videos. Sometimes it crashes during loading process - when all vids in the deck are not finished loading.
2. It crashes while loading and I assign - before finished loading every single video - a clip to a layer.
3. When I use Flash footage it increases the Chance of Crashing