Closed goldshtn closed 9 years ago
Tracked this down to CLRMD's DbgEngDataReader.Dispose
not cleaning up the IDebugClient
completely, so it will still have lingering output callbacks until the next GC-finalize cycle.
Fixed in a010785a28b536a9c4cd10e6563a0dcec3f161e7 by changing the Dispose
method appropriately.
For example, open a dump file and run
.dem
. Quit withq
. Repeat.dem
again. Quit withq
. Every time you enter with.dem
, there is some engine output repeated multiple times. It seems that our call to SetOutputCallbacksWide is somehow being persisted across multiple DataTarget instances...