Ok, thanks for your answer.
Do you know how could I detect a memory leak that doesn't appear in the memory profiler tool of Visual Studio?
Also, being 1GB of RAM occupied, it certainly has to be about pictures, do you know if there is a way to "retain" pictures data inside the app's heap instead of the web cache that we could accidentally have done?
For example: I start a diagnostics session for "Javascript Memory" and take some heap snapshots after using the app for 2 minutes, the task manager tells me the app consumes about 100MB but when I look at the heap snapshot, it tells me that it's about
10MB...