Requesting help with memory leak in WorkMonitor sample
I’m using the very cool WorkflowMonitor sample as a starting point for my client-side application to get status on currently running workflows in my system. Unfortunately, I’m finding that it has a pretty bad memory leak. In the list of workflows (upper-left panel), if you repeatedly click on different workflow instances, the memory consumption for the application just keeps going up and up. The memory doesn’t get freed even after garbage collection, so I’m pretty sure it is a real leak. I’ve tried to debug into it, and even tried using the CLR profiler to figure out what’s going on … it definitely has something to do with hosting the workflow designer, and unfortunately the designer re-hosting code is pretty complicated and I really can’t hope to find the bug myself. It could be just a bug in the sample, or a bug in the product. Is there anybody who can help me? Perhaps the author of this sample, whoever that is? This sample is a pretty important part of what I’m trying to do, and if I can’t get this leak fixed, I’ll have to do without the pretty workflow designer view, which would be a real shame … I’ll have to resort to displaying the workflow status textually rather than pictorially.
Thanks,
Rajeev
