Ultimate 2017.1.1 triggers OOM in VS 2015 Update 3

I'm working with a large solution (VB.NET) - about 31 projects, about 900,000 lines of "active" code.  After using VS 2015 for about 4 hours, multiple debug sessions, it will suddenly start to slow down (end basic typing in the VS code editor is very slow).  I'll touch nothing just leave the code at a breakpoint and sit back and watch TaskMgr reporting memory usage for VS 2015 ... it just keeps increasing and increase until it eventually OOMs (out of memory error) after hitting 4GB address space max.

If I uninstall ReSharper 2017.1.1 and do the same days worth of debuggings/working with my solution, I don't get any OOM errors, well below 4GB ... usually around 1.7 GB usage.

So "something" in ReSharper 2017.1.1 appears to have a rather significant memory leak.

Any suggestions on what feature in ReSharper might be causing this OOM problem?

Cheers, Rob.