0
0

First off, I’m using version 3.70. I have a screensaver I’ve written that continually loops a playlist of songs. I’ve noticed that if I leave it running over night (or any extended period) I get strange crashes. If I disable sound, I have no problems. But when I enable it, I get everything from a standard Access Violation error all the way up to a SPONTANEOUS SYSTEM RESTART (in XP no less)!

The lastest and most detailed error I’ve been able to track down was an access violation caused in “WMVCORE.DLL”.

Is there any information whatsoever someone could give me to give me a clue as to what steps I should take to prevent this? Is this perhaps some kind of known bug in the current version of FMOD?

The fact that some of the crash problems I’ve experienced when using FMOD in my screensaver over a prolonged period are the sort that actually cause the system to restart (and I get the notification afterward that Windows has experienced a serious error) leads me to think it’s not my code but something FMOD is doing. My code is nothing more than some loops here and there. Were it a stray pointer or something, I’d expect to just get an access violation message – not a full system crash. Is anyone aware of either issues with FMOD that could cause this, or perhaps improper use of the FMOD API that could cause this when used over a prolonged period (several hours) of looping through playlists of music?

Thanks!

  • You must to post comments
0
0

The content is arbitrary, but can include WMA. I’m pretty certain this has to do with WMA though, as you said, this is all WMVCORE has to do with.

I’ll try to do isolated tests with WMA and non-WMA content. If it turns out (as I expect it will) that it is only with WMA (or ASF?) content, what steps can I take to guard against these kinds of crashes? Would simple try-catch blocks perhaps make it possible to “hop” over these problems? I mean, in some cases it appears to be resulting in a full-on SYSTEM CRASH. My product is preparing to ship retail within just a few days so I’ve got to come up with some way to ensure my product doesn’t cause my user’s machines to completely crash even if it isn’t my fault.

Any ideas on how to handle and/or prevent this even though the code that may be the problem is out of our hands?

Thanks!

  • You must to post comments
0
0

Yeah, I’ve been running the app on 4 very different spec computers for days now… The problem is that the problem is very intermitant (sp?). And it usually takes several hours of running before it occurs (like 6-12 hours!). But sometimes it’s only a handful of minutes. Needless to say, this makes it a VERY difficult problem to track down.

I’ve been sent logs where it happens and there are only two songs queued. These same 2 songs play over and over and over and then suddenly there’s a crash. So I tend to think it’s not an issue of a corrupted audio file since it played those same songs several times without error.

I do have a stream end callback set and then a FSOUND_IsPlaying() check in a loop to catch WMA and ASF files since you can’t set end callbacks for them. Is it possible that somehow double-checking in this way that perhaps somehow my app may try to close the same stream twice or something? Could this potentially cause a problem?

Also, I’m no expert on exception handling by any means… can anyone offer tips on how I might be able to handle these exceptions and avert a system crash?

Thanks for your help, brett!

  • You must to post comments
Showing 2 results
Your Answer

Please first to submit.