testing Arena 5.0.1 crash

[DHoude]

So I am getting some testing done for my NYE set. It was the first time I have run the system all together. I got a crash about 8 hrs in and i have the error log too.

My setup is Win 7 64 bit - Resolume Arena 5.0.1 into Spout 2.0.4 then into Virtual DJ 8.1 b2587 for final display. I don't think it will easily happen, but here are the details:

Faulting application name: Arena.exe, version: 0.0.0.0, time stamp: 0x5652ec62
Faulting module name: Arena.exe, version: 0.0.0.0, time stamp: 0x5652ec62
Exception code: 0xc0000005
Fault offset: 0x003e2af6
Faulting process id: 0x1458
Faulting application start time: 0x01d12e154fa8b7f1
Faulting application path: C:\Program Files (x86)\Resolume Arena 5.0.1\Arena.exe
Faulting module path: C:\Program Files (x86)\Resolume Arena 5.0.1\Arena.exe
Report Id: 2056f64a-9a54-11e5-be9a-ac7ba11e01f8
Faulting package full name: %14
Faulting package-relative application ID: %15

Here is the EVT full view

I clean reinstalled Windows 7 at the beginning of November to clean up. All latest NVIDIA drivers, software etc. I can look a bit later and know computers. Any idea of what else I can provide to research this?

EDIT:
To add, this next event was at the close of Arena when i found it almost 1 hour later.

Fault bucket 417599706, type 25
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
P1: Arena.exe
P2: 0.0.0.0
P3: 5652ec62
P4: Arena.exe
P5: 0.0.0.0
P6: 5652ec62
P7: c0000005
P8: 003e2af6
P9:
P10:

Attached files:
C:\Users\Owner\AppData\Local\Temp\WERA52E.tmp.WERInternalMetadata.xml

These files may be available here:
C:\Users\Owner\AppData\Local\Microsoft\Windows\WER\ReportArchive\AppCrash_Arena.exe_719dba45a09a810a1796628ba2db3e514d63590_1ab65348

Analysis symbol:
Rechecking for solution: 0
Report Id: 2056f64a-9a54-11e5-be9a-ac7ba11e01f8
Report Status: 0

[DHoude]

Still digging for this, but I was surprised to see this about 4 hours before the crash in my event logs.

Fault bucket 1535666489, type 5
Event Name: RADAR_PRE_LEAK_WOW64
Response: Not available
Cab Id: 0

Problem signature:
P1: Arena.exe
P2: 0.0.0.0
P3: 6.1.7601.2.1.0
P4:
P5:
P6:
P7:
P8:
P9:
P10:

Attached files:
C:\Users\Owner\AppData\Local\Temp\RDR3DD1.tmp\empty.txt

These files may be available here:


Analysis symbol:
Rechecking for solution: 0
Report Id: f8f36abe-9a39-11e5-be9a-ac7ba11e01f8
Report Status: 0

[Joris]

Sorry to hear you're having crashes. Crashes suck.

Unfortunately, those error reports don't tell us much. The actual code has all been compiled away, so it's just machine speak.

These type of random crashes are very hard to track down. And unless you have a specific set of actions that will trigger the crash, they are even harder to fix. It's very hard to change something if you don't know the exact scope of what you need to change.

I understand you are keen to get to the bottom of this. In our experience. a random crash after an extended period of normal operation, usually is caused by running out of memory.

Resolume is currently still a 32 bit app, but doesn't limit you in the amount of files you can load. So the responsibility for keeping an eye on your memory use is in your hands. I'd be very interested to hear what your memory use is like during your 8 hour set.

When you take care to strictly use DXV files only ( this includes not using JPEG or PNG files! ), it's very, very hard to get Resolume to crash.

[DHoude]

Thanks, yea I get that it does not give much. I have been working with the developer of Spout too on a few things.

He pointed me in the direction of Googling "Exception code: 0xc0000005", which seems to be an Access Violation. I tracked down a thread that mentions a bunch a different methods to approach this.

1. The top was Reg key - When I installed Arena 5.0.1 it seemed to go in parallel. So I had to uninstall 5.0.0 manually. This weekend I used CCleaner and it found some old registry entries of 5.0.0. I don't think it caused anything, but cleaning up can't hurt.

2. Run program As Admin - I am an admin on this machine, but I set it in the properties to run as admin. I figure it can't hurt anything.

3. Ram and SSD disk test - I have done a ram test and passed. Looking into testing the SSD next. It is not that old, but that does not mean much either.

Those applied to the problem the most to me. But I went through each step to see how ideal I can get. I also looked at all errors in the event logs and tried to address anything possible. I am actually running smoother now when I run "Latency Mon" tests, so bonus there.

As far as DVX 3, everything has been encoded in DXV 3 well before this. I do have some PNG files, not large masks just smaller graphics. No JPEGs at all. I have encoded all those as DXV 3 too, but FPS seemed to drop more with those files. The PNGs seem to behave better. But I hear you, I will keep an eye on mem management.

As far as the test, I really just ran the mask technique (3 HD videos) for the entire 8+ hrs. Output to Spout and then into VDJ to emulate worst case. I wanted to stress test it and check in every now and then. Any good tools to use to keep an eye on memory or clean up if it is getting out of control?