Sep 29, 2010 at 5:32 PM
Edited Sep 29, 2010 at 5:41 PM
Thanks for reporting that, since it might help to users with similar scenarios. The approach that you used for removing the view seems to be correct.
On the other hand, if you do not have any other reference to the views in your application, they should be removed when the garbage collection occurs. But this is not possible to predict when it will occur. Probably, this is why you are
seeing that your memory are going up.
I would recommend you to try adding a button (in the toolbar of your app) that force to collect to the garbage collector using the following code:
public void YourButtonClickCommand(object Object)
Then if after executing this code you realize that your memory is released, it means that you do not have a leak over there. But if this does not release, I would recommend you to check if your application keeps a reference of your views (e.g. your
Please take into account that this is just a test. After this test, you have to remove this from your application.
If you continue experiencing this situation, could you send a repro sample?.
I hope this help.