I created a "development test" toexercise a set of classes from production code that are responsible for a task that leaks memory every time it is done, according to process explorer.
The code seems to leak 2MB each time and does not stop until the system memory is exhausted.
When I run the development test in debug, it completes and exits with code 0 within 5 minutes.
When I profile it with Inspector XE, the anlysis never completes, not even if I leave it over night.
What should I be trying? What should I look at?
I've also tried the Inspector configuration option to step through with the debugger to a break point for start of profiling and another breakpoint for stop of profilingand that exercise causes inspector to throw an unhandled exception and crash.