Similar to memory warnings:
- Article object memory
- Images in memory
- Section controllers in memory
Currently not valid with the latest changes:
- WebView cache
• BGerstle-WMF | |
Jan 28 2016, 10:22 PM |
F4164892: WMFArticleImageGalleryViewController unpaired retain:release log.txt | |
Jun 14 2016, 2:23 PM |
Similar to memory warnings:
Currently not valid with the latest changes:
Status | Subtype | Assigned | Task | ||
---|---|---|---|---|---|
Resolved | None | T124236 EPIC: Investigate 5.0 app performance | |||
Resolved | JoeWalsh | T125156 As a good platform citizen, the app should purge all cached memory objects when going to the background |
@JoeWalsh wrote this on github too… but then I closed the pr…
Did you see what the memory savings were with this change… just curious on how much we are saving - and what the total looks like right now
So after tapping about 20 images in the Obama article and simulating a memory warning, we were stuck at 177MB before and are now at 106MB. This is simulating the worst case- entering and leaving the gallery for every image.