jvalenzu

Thanks for the response - I guess I'd assumed that a class that extends a dynamic class must be dynamic. Obviously I'm a flash neophyte. After some slightly more rigorous testing I think the problem I'm seeing is attributable to the gc being invoked during unload. Setting DisplayObjectLoader.defaultAutoForceGC, explicitly invoking unloadAndStop(false) for _loader, and some reordering how we invoke the LoaderMax calls (I don't think these are relevant, but can't rule them out) seem to fix us up. I'll probably hold off upgrading unless it's really necessary, but if I do I'll report back any differences. Thanks again for the help!

We're running 1.895 here. Just to clarify, we have some loaders using LoaderMax and some not using LoaderMax, but they both run simultaneously. It's not possible at the moment to just flip a switch so that we're entirely using LoaderMax or not-LoaderMax, so I can't say with certainty that it's the problem - it's entirely possible the error is in the way we're using it. I don't think it's the unloadAndStop: I made a subclass of SWFLoader and removed the property on the loader before invoking it. This should rule that out, right? public class IgSWFLoader extends SWFLoader { // ... override public function unload():void { if (_loader && _loader.hasOwnProperty("unloadAndStop")) delete _loader["unloadAndStop"]; super.unload(); } }

Well, the problem doesn't seem to be restricted to unloading any particular file. It's not really possible to just drop in a generic replacement, but I'll see if I can get simple test case up. Is there something specific I should be looking for in our assets that might cause a problem? I'm disinclined to this it's a Flash problem - we have non-LoaderMax loaders present in the application as well and they don't seem to exhibit the problem - but I can't rule it out. I'll see if I can narrow it down in any case.

Yeah - removing the calls to unload/dispose solves the problem. I thought for a bit it might be the explicit garbage collection but setting DisplayObjectLoader.defaultAutoForceGC to false doesn't seem to change anything. This is with a LoaderMax instance with ~197 swfLoaders with completed status. Anything else I should try?

Any update on this? I'm explicitly calling unload/dispose on swfLoaders I'm done with and the regularly get drops down to 2fps.