New Post: WPF & Prism 4.1 Garbage Collection / Memory Issues

Hi,

So far I couldn't find the cause of this problem reviewing the code snippets you posted above. Also, I am unable to see the graph you linked below (I just sent you a access request for it).

Based on my understanding, the action of simply instantiating the view in the module (like in the code snippet) would not cause a memory leak. Also, as far as I know, weak references should not prevent an object from being garbage collected, so this might not be the cause behind it (although, I am not seeing anything that might create a weak reference in the code snippets either...)

It would be helpful if you could provide us with more information about your scenario so that we can help you further with this. For example, it would be useful to know what data bindings are being done against the RemoveView property and where. Also, I believe it could be worth checking if this issue is also present when using a different type of region, for example an ItemsControl or ListBox .

Thanks,

Damian Cherubini
http://blogs.southworks.net/dcherubini