Note that there are some explanatory texts on larger screens.

plurals
  1. POWP7 - Xaml Pages and Peak Memory problem
    primarykey
    data
    text
    <p>I have a problem with 90mb peak memory limit issue.</p> <p>For example: I create 1 Panorama Application(with default content) and add 3 PivotPages or 6 Portrait Page(Page A and Page B.. with blank content). Each time I navigate and go back between these pages the memory usage is going higher and higher. At the end, It passes the 90mb limit.</p> <p>I use buttons to navigate like this:</p> <pre><code>private void btn1_Click(object sender, RoutedEventArgs e) { NavigationService.Navigate(new Uri("/PageA.xaml", UriKind.Relative)); } </code></pre> <p>Do I miss something important while navigating between pages? While searching for a solution I heard about garbage collector? How can I use it or do I need to?</p> <p>I couldn't find an answer for that; I found this similar topic: <a href="http://forums.create.msdn.com/forums/p/76007/466968.aspx" rel="nofollow">http://forums.create.msdn.com/forums/p/76007/466968.aspx</a> but there isn't a final solution.</p> <p>Note: I am using Coding4fun toolkit to measure memory usage.</p> <hr> <p>Edit: I created a sample panorama application with some pivot pages (1 with content). </p> <p><a href="http://i54.tinypic.com/zfip.jpg" rel="nofollow">http://i54.tinypic.com/zfip.jpg</a></p> <p>At start, application opened with 30mb. After I navigate to the same pivot page a couple of times, Peakmemory started to increase little by little and stoped at 47mb. Is this normal? Maybe, I didn't understand the dynamics of this application building stuff. But it doesn't make sense if it keeps increasing the ram usage and makes application crush after some use.</p>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload