Give that memory back!
A weird behavior (one more) I noticed on Windows Phone, thanks to a question on StackOverflow (once more). First, let’s create a simple Windows Phone application. The first page will contain three buttons: the first one navigates to another page, the second one displays the amount of memory used (by calling Microsoft.Phone.Info.DeviceStatus.ApplicationCurrentMemoryUsage), and the last one will forcefully call the garbage collector, wait for the finalizers to execute, and collect the memory freed by those finalizers: In the second page, we simply create a few objects and bind them to a grid. The sole purpose is to simulate a page that would use a largeRead More →