It is not an UI problem, the "Bar" is never ever released, this is a memory leak for a shared resource
of course what I wrote is a simple example, but in case of complex app with shared resources, the "bar" should be deallocated
See the "Bar" as a db connecting layer, I do not want to be allocated when the tab is not selected, and this code is a simpler an example for that (when disappear, deallocated object)
Post
Replies
Boosts
Views
Activity
May the problem in this thread be related (and not resolved) ?
I do not want to see the transition, I've a memory leak, Bar instance is never released