There's a bug in the way WPF manages memory for bitmaps that is causing our application to "lock-up" with 99% time in GC for minutes on end. It's already in Connect here:
But it's been closed as "By Design" with no comment.
If you look at the code in MS.Internal.MemoryPressure.ProcessAdd() then you can see that it resets it's timer before calling GC.Collect(2). That means that if the GC takes more than 850ms (due to the application having lots of valid objects on the heap that needs traversing during a GC) then it will happenevery time you create a new WriteableBitmap. That is VERY bad for us.
How can I get the bug re-opened in Connect? Is there any way at all (e.g. creating a support incident)?