Page 1 of 1

Direct Show Player Causing APPCRASH

Posted: Mon Nov 21, 2016 8:18 pm
by studawg66
I have an app built in an old version of RunRev that I'm trying to get stable in the newer 8.1 or 8.1.1 releases. It seems to do everything well, including play my multicast streaming video (thanks to the new DS player!), but if I leave the program running for several days the app eventually crashes. This is an app that must run 24x7, so that is unacceptable. The last two times I captured the crash, it was after 3 days running with a video stream. After checking the latest crash log, it shows that the DS player is the culprit. Any ideas? See log below:

Problem signature:
Problem Event Name: APPCRASH
Application Name: CLOCKS~1.SCR
Application Version:
Application Timestamp: 57d6e85c
Fault Module Name:
Fault Module Version:
Fault Module Timestamp: 4e2863cc
Exception Code: c0000005
Exception Offset: 0000b5d5
OS Version: 6.1.7601.
Locale ID: 1033
Additional Information 1: 8e76
Additional Information 2: 8e7601b6ffa93b60ed9eeebc17d46d7d
Additional Information 3: 6595
Additional Information 4: 65950c9b20136d6060c808617265b87b

Re: Direct Show Player Causing APPCRASH

Posted: Mon Jan 23, 2017 8:56 pm
by studawg66
Bump. Anyone? I still haven't found a solution to this.

Re: Direct Show Player Causing APPCRASH

Posted: Tue Jan 24, 2017 6:21 pm
by jacque
Crashes are always engine bugs so your best recourse is to report the problem at the bug database here:

Since the crash only happens after an extended period of time, it sounds like a memory leak. This could easily be something in the scripts, which means you can fix it yourself, or it could be a bug in the engine that LC has to fix.

You might want to test using the latest LC pre-release version 8.1.3rc1. It won't solve the problem but it is supposed to handle low memory conditions better.

Re: Direct Show Player Causing APPCRASH

Posted: Tue Feb 07, 2017 8:22 pm
by studawg66
Just an update on this...I have been running this app in 8.1.2 for a few weeks now and have not seen this appcrash. So I'm not sure what changed that would have helped this, but maybe they found some memory issues that they resolved. I'm going to assume it is fixed and move on.