Open poliahrameshkumar opened 4 years ago
@poliahrameshkumar Can you please attach a small project that demonstrates this issue? Thanks!
@samhouts you can create a two page application and put some large image file in second page. You can try to pop the second page to go to first page. It will not release the memory of the second page. You can create this simple project and check.
@poliahrameshkumar can you post some screen shots of the objects you see leaking?
I think this static array is leaking https://github.com/xamarin/Xamarin.Forms/blob/7a9b54dae9605169f0417c168af2cd81f931b2a9/Xamarin.Forms.Core/Layout.cs#L62
But I'd still like to see what you see so we can see if it's what we're all seeing
@PureWeen Sorry to say, my Xamarin.Profiler got expired after one month. So, now I can't check. If someone with access to profiler checks this, it would be helpful.
@poliahrameshkumar were you testing with a brand new app? or your own app?
Do you have a repro of the app you were testing with we can check?
@PureWeen My own app. But in every app It will be reproducible.
It's going to possibly vary app to app and in some apps it's the users fault
We can look into what I found but there's a chance it's not what you found.
My issue is related to this issue https://github.com/xamarin/Xamarin.Forms/issues/1429
Any news on this issue? Please see the repro project below https://www.dropbox.com/s/991aw7u7667skgg/MemoryTest.zip?dl=0
Steps to reproduce (please use an actual device, not a simulator) :
Just discovered this memory leak in my app as well. Is there any update on this issue? Or any known workarounds?
I'm currently having the same issue with my app. It's been over a year since the last post, any progress? Or is there a workaround?
Description
When we use PopAsync in Xamarin.Forms, the memory of popped page is not getting released. This was observed on iOS based on Xamarin.Profiler and app performance.
Steps to Reproduce
Expected Behavior
Memory should get released
Actual Behavior
Memory is not getting released
Basic Information
Screenshots
Reproduction Link
Workaround
No workaround is found so far.