Comments on: RobotLegs, mediators and memory leaks

By: Randy

Randy — Wed, 05 May 2010 19:58:11 +0000

@shaun Thanks for the link and your twitter response. In my case I just modified my mediator mapping like this:

mediatorMap.mapView(Map, MapMediator, Map, true, false);

so that the creation is automatic but the deletion isn’t. Just a coincidence that the view is a map … as in Yahoo map :-0

By: Matan Uberstein

Matan Uberstein — Wed, 05 May 2010 19:19:53 +0000

Nice one Shaun!

By: shaun

shaun — Wed, 05 May 2010 18:51:35 +0000

Dear Anonymous,

Robotlegs is Open Source: you could have filed a bug report or even fixed the code yourself, but you chose to moan.. thanks for the feedback.

By: shaun

shaun — Wed, 05 May 2010 18:16:20 +0000

With auto-mediation (the default when mapping a mediator) mediators are created and removed automatically as view components arrive on and leave the stage. The mediator is supplied with an EventMap that you can use to wire up your listeners, and when the mediator is removed it’s listeners will be removed along with it. Also, you don’t have to use auto-mediation, you can create, register and remove mediators manually too:

http://knowledge.robotlegs.org/discussions/questions/117-any-other-way-to-create-mediators-other-than-listening-to-added_to_stage#comment_1363130

By: Anonymous

Anonymous — Wed, 05 May 2010 17:32:50 +0000

Another fun thing about the interaction of robotlegs mediators and states. Its possible for the state change to cause robot legs to create a mediator through the mediator map. This is what you discovered. Whats annoying is that under certain conditions the onRemove can get fired BEFORE the onRegister does. The onRegister function is fired by mapping an event listener to the creation complete event. If the application for some reason starts the mediator then quickly decides to change state again then it will fire that onRemove before your component thats tied to the mediator has a chance to fire creation complete. Drop into the the base class for the mediator map and you can see that the event handler is not removed in the onRemove function…but only once it has fired in the creation complete handler. wheeee!