ParsleyModuleInfoProxy memory leak

Forum|Forum|15 years ago
June 30, 2010
2 replies
1342 views

Whenever you create a module using the Cairngorm Module 0.9 library, a ParsleyModuleInfoProxy object is created that is never garbage collected since there are hard references to the Parsley Library. Here is a screenshot of a couple of those paths

http://skitch.com/jeffknight/dk15h/flash-profile-cairngorm-parsley

The module is being cleaned up correctly when the s:Window is closed, however these proxies stick around. I am using Parsley 2.2.2 for Flex 4

Cairngorm

This topic has been closed for replies.

S

SpecialKAuthor

Participating Frequently

When will we see the next point release of the Module Library with these fixes included?

A

Alex Uhlmann

Participating Frequently

Depends on feedback, maybe next week.

S

SpecialKAuthor

Participating Frequently

Excellent. We are prepping to push a release to 1 million+ users which will be making extensive use of this library in about the same timeframe.

S

SpecialKAuthor

Participating Frequently

Update: this seems to be related to ParsleyModuleManager.getModule(). Whenever you call this function, it creates a ParsleyModuleInfoProxy object that it pushes into the ParsleyModuleManager.infos array. This object is then never removed.

A

Alex Uhlmann

Participating Frequently

You're correct, that's a bug. I've filed it here. Also, note we face another issue around styles with the module library at the moment. Let us know if you have ideas for a fix. Feel free to post to the forum or submit a fix.

A

Alex Uhlmann

Participating Frequently

The styling issue is fixed, the memory leak should be fixed with this:

http://forums.adobe.com/thread/672574?tstart=0

Let me know if you still see the leak, I've not tested it yet.

Sign up

To post, reply, or follow discussions, please sign in with your Adobe ID.

Sign in to Adobe Community

To post, reply, or follow discussions, please sign in with your Adobe ID.

Scanning file for viruses.

This file cannot be downloaded