问题描述:

I've stuck with memory profiling of WP8 application. I am trying to detect the cause of memory leak when user navigate from page 1 to page 2 (page 2 has WebBrowser control on it) and back to page 1 repeatedly. To figure out where memory leak is, I am using Windows Phone Application Analysis from Visual Studio 2013 Update 2. I've read several articles about memory profiling using WPAA, including series of articles:

  • Memory Profiling for Application Performance
  • Memory Profiling: Launching, Graphs and Markers
  • Memory Profiling: The Heap Summary view
  • Memory Profiling: The Types View
  • Memory Profiling: The Instances View
  • Memory Profiling: The Methods View
  • Memory Profiling: The Object Graph View

I've done several memory profiler sessions and found out observations I can't explain and understand. According to memory profiler's Heap Summary total memory went down in selected time range, but according to graph - memory usage significantly grown, I can't understand data obtained using memory profiler taking into account knowledge I have so far in memory analysis. Here is a screenshot of profiler's session.

  • Does anybody know what kind of problem could possible cause such a strange profiler's observation?
  • What to next taking into account observed data, should I continue looking for leak in visual controls or non-visual objects?

相关阅读:
Top