I would at least assume that memory leaks are not caused by Metro or SharpDX.
Check this out: C # memory leaks
(Or just look for SO for "C # memory leaks.")
Once you have passed the checklist of things extracted from the above link / search query, go on to check the code associated with SharpDX / Metro. The best recommendations came from my mother when I was young: "Get out after yourself when you finish playing." Dispose of objects when you are finished with them, do not leave databases, files or memory streams open longer than you need. This is the reason for many memory leak problems, including mine.
source share