J
joy scott
I have a problem with a C# managed COM Add-in, that looks like a memory bug,
and need some advise on how to debug.
The bug can occur at different points in the code (ie. vary from build to
build).
One example of how it happens is when the addin starts up, OnStartupComplete
is run, this instantiates a WordAppEventHelper object which in turn
instantiates
another object. In the constructor of this last object, a string is
initialized.
This string initialization causes the bug to occur. The symptoms are
a) WINWORD.EXE starts to take approx 90% of CPU
b) When I try to insert a text box, nothing happens (insert your drawing
here appears momentarily and then disappears)
Now, the Add-in uses a Shim, which I thought executed the addin in it's own
application domain. So, i'm not sure how a memory bug like this could occur.
I would be interested in any suggestions in how to debug. Thank you
and need some advise on how to debug.
The bug can occur at different points in the code (ie. vary from build to
build).
One example of how it happens is when the addin starts up, OnStartupComplete
is run, this instantiates a WordAppEventHelper object which in turn
instantiates
another object. In the constructor of this last object, a string is
initialized.
This string initialization causes the bug to occur. The symptoms are
a) WINWORD.EXE starts to take approx 90% of CPU
b) When I try to insert a text box, nothing happens (insert your drawing
here appears momentarily and then disappears)
Now, the Add-in uses a Shim, which I thought executed the addin in it's own
application domain. So, i'm not sure how a memory bug like this could occur.
I would be interested in any suggestions in how to debug. Thank you