Memory release

[kojot1234]

Calling AssetLibrary.removeAllAssets(); Will generate a null obj ref. (_methods)

Line 647-649 (DefaultScreenPass.as):
for (var i : uint = 0; i < _methods.length; ++i) {
addPasses(_methods[i].method.passes);
}

There should be a null check for _methods. When running
if (_methods != null) {
for (var i : uint = 0; i < _methods.length; ++i) {
addPasses(_methods[i].method.passes);
}
}

Also when disposing all bitmapData should be released.
Including _mipMaps in BitmapTexture.

[richardolsson]

The removeAllAssets() function will dispose the assets, and you should not try to use the assets after they have been disposed. The purpose of the dispose() functions is to make an object available for garbage collection. Have you found that objects are not garbage collected after they have been disposed?

[kojot1234]

Yes it does not seem to dispose _mipMaps Array in BitmapTexture.

[richardolsson]

There is no need to "dispose" an array. As long as the array is not being directly or indirectly referenced by the root display list of your application, i.e. as long as you don't keep a reference to the texture lying around, it will be garbage collected.

[kojot1234]

That's weird because the bitmapData that referenced inside that array did not get disposed so maybe there is a reference to it. I have used sharedContext with Starling for my project. I can dig deeper and report back.

[richardolsson]

Well, regardless I guess it doesn't hurt to explicitly dispose. We'll make sure that happens in the next development cycle.

[kojot1234]

Thank you, I'll still try to help out.