This content has been marked as final.
Show 10 replies
-
1. Re: Aggregator errors
emcod Mar 3, 2009 4:13 PM (in response to emcod)Update:
I'm not sure if it's related to the errors or not, but the aggregator course is also causing severe performance issues with the computer I'm testing it on. Both memory and CPU usage are maxing out, at least while the course is loading. Seems to level off somewhat after a few moments, but still remains fairly high, causing embedded Flash animations to be choppy or not play at all.
Still going to test on another machine ... I'll post what happens. -
2. Re: Aggregator errors
emcod Mar 3, 2009 4:34 PM (in response to emcod)Update 2:
Just confirmed that I'm having the same issues when I compile the aggregator course on my Win32 machine, though I'm not actually seeing the error messages during playback ((I must have AS error checking turned off on that machine).
I'm also seeing (or hearing) some bizarre audio issues, with audio from different SWFs playing simultaneously.
Help!! -
3. Re: Aggregator errors
macrofireball Mar 4, 2009 1:11 AM (in response to emcod)Hi there,
[quote]I'm also seeing (or hearing) some bizarre audio issues, with audio from different SWFs playing simultaneously. [/quote]
Are you by any chance viewing your published Aggregator project through Firefox? I have encountered and this reported in FF. At present this doesn't seem to occur in Internet Explorer.
As for the Flash Player Errors you are encountering I would strongly recommend that you report these to the Adobe Captivate team.
Adobe Captivate Feature Request/Bug Report Form
Regards - Mark -
4. Re: Aggregator errors
emcod Mar 4, 2009 1:58 PM (in response to emcod)I've tested the course in IE, FF and Chrome with the same results.
I discovered with further testing that the first SWF in my project appears to be the culprit in hogging system resources, so I'm hoping that debugging that will solve other issues. I'll let you know what happens. -
5. Re: Aggregator errors
KCWebPlaza Mar 4, 2009 4:40 PM (in response to emcod)My guess is it's a memory leak. As movies are load/unloaded, memory issues are creeping in. I'd also guess that the fix would need to come from Adobe (i.e. patch). -
6. Re: Aggregator errors
emcod Mar 4, 2009 10:06 PM (in response to emcod)Not sure if it's a memory leak -- CPU is actually getting hit harder than memory -- but I am going to submit a bug report. Thanks.
Tried removing the first section completely from the aggregator project, and still having the same issues. It does seem to have something to do with the aggregator, since the sections run fine as standalone movies (with or without a TOC). -
7. Re: Aggregator errors
macrofireball Mar 5, 2009 1:53 AM (in response to emcod)Hello again,
I am sorry to hear that you are still experiencing problems. Would you mind telling us know what response you get back from the Captivate team? I would really like to know what is causing this issue. :-)
Best - Mark -
8. Re: Aggregator errors
emcod Mar 13, 2009 1:08 AM (in response to macrofireball)The Captivate team responded, but hasn't been able to help so far. From my own experimentation, it looks like the errors were related to my using AS3 for the course. When I switched all of the Captivate movies to AS2, and created the Aggregator project as AS2, the errors went away, and performance was greatly improved.
BTW, it does look like a memory leak was part of the issue before. Memory was not being released when a new SWF loaded, so by the time I got to the end of the course, it was using 700-800 MB of memory.
Dealing with another issue now. The AS2 Aggregator course works great in Firefox and Safari, but in IE7, the preloader shows up, but the first movie won't load. Looking up info on SWFObject, but not having much luck diagnosing this new issue. Sheesh! -
9. Re: Aggregator errors
emcod Mar 17, 2009 12:09 PM (in response to emcod)Fixed the last issue by updating to the latest version of Flash Player 10 (I was using v10 before, but an incremental update was available when I checked). -
10. Re: Aggregator errors
steve tom Mar 23, 2009 8:39 AM (in response to emcod)So I don't know if this will help your problem, but I had the same error. I was loading an external swf made Captivate into an a custom interface and this error was being thrown. So after some digging it turns out that one of my click areas had quiz reporting turned on in the properties. I unchecked it and the it worked.
-Steve

