> I'm investigating the current memory corruption with the refactor. I've attached the trace log:
[COM Interop trace.xlsx](https://github.com/rubberduck-vba/Rubberduck/files/3390178/COM.Interop.trace.xlsx)
*Methodology*
To reproduce the memory corruption, I executed this at VBA immediate window:
```
?Application.VBE.Addins("Rubberduck.Extension").Object.DocumentAll
```
and using breakpoints, allowed the code to get into the loop for `typeLib.Document` but not actually execute it, an