I have since realised that the reason for the increasing memory usage was due to the use of a Frame, which would store a history of past pages. By setting Frame.JournalOw nership to UsesParentJourn al, this problem is avoided.

This is my first question here, so apologies if I have made a mistake.

I am developing a collection of small games using WPF with C# but have been having real difficulty in being able to load and unload each game into my main viewer application.

The structure of my program is I have a main view application GameViewer.EXE which basically consists of a Frame object to view pages.
Each game is a custom class GamePage.CS,...