#HELP! AAPLAY mem leak!
6 messages in this thread
I'm using AAPLAY.DLL in a screen saver application. The application crashed
after running continuously for about 24 – 30 hours. I've tried several
versions of AAPLAY.DLL (all dated in 1993, the most recent was dated in
December), and they all have the same problem, some worse than others (one
crashes after only 4 hours).
What is causing this? Is this a bug in AAPLAY.DLL? Is there a more recent
version than December 1993? Can you offer any help/advice?
I tried running the flic with just the Autodeck Animation Player for Windows,
and after running the 640×480 flic full screen for about an hour, about 1 KB of
Windows memory disappeared…
Help!
Paul Unterweiser, M!ND GAMES new media
Hi Paul,
<< The application crashed after running continuously for about 24 – 30 hours.
>>
Thanks for the bug report. It was reported a few months back. At this time, I
do not have any additional details regarding a fix.
jonas[adesk]
Jonas,
> Thanks for the bug report. It was reported a few months back. At this
> time, I do not have any additional details regarding a fix.
Ouch! This could be a big problem for me, can you tell me if there is some I
can talk to to follow up on this? Is there a work-around? Any ideas where the
problem lies? Is it a memory problem, or what?
I know of literally dozens of commercial apps that are using or including your
AAPLAY.DLL, is this a priority project or on the back burner?
Paul Unterweiser, M!ND GAMES new media
Hi Paul,
<< can you tell me if there is some I can talk to to follow up on this? >>
Start a dialog with Brian Rudolph[adesk]. He's following this issue.
jonas[ades]
<<Ouch! This could be a big problem for me, can you tell me if there is some I
can talk to to follow up on this? Is there a work-around? Any ideas where the
problem lies? Is it a memory problem, or what?>>
There appears to be some type of memory leak, we are still investigating the
issue. I don't have any information at this time concerning a bug fix or new
release of the player.
What other developers who are doing kiosks or other applications where the
player is running for hours at a time have done to work around the problem is
to read the system clock and periodically shut down one instance of the player
and start another.
-Brian
Brian,
Thanks for the reply…
> What other developers who are doing kiosks or other applications
> where the player is running for hours at a time have done to work
> around the problem is to read the system clock and periodically shut
> down one instance of the player and start another.
Hmmm… What if I created an .AAS script that played the FLC then a single
.BMP then loop back, would that do it? Or does the application have to unload
AAPLAY.DLL entirely, or just the FLC?
BTW, could you e-mail me your voice address? I'm in a -major- rush to fix this
before we ship this application to -the masses-.
Paul Unterweiser, M!ND GAMES new media