You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There are multiple memory leaks ranging from tiny (12 bytes each time) to somewhat serious (several dozen KB) in mscordacwks's implementation of the IXCLR* interfaces. Specifically, it doesn't seem to be hardened against invalid input. There is one repro here and you could construct many more. Notably, DacError uses the EX_THROW macro, which seems to leak 12 bytes of memory because it allocates the exception object with new (?!).
The text was updated successfully, but these errors were encountered:
There are multiple memory leaks ranging from tiny (12 bytes each time) to somewhat serious (several dozen KB) in mscordacwks's implementation of the IXCLR* interfaces. Specifically, it doesn't seem to be hardened against invalid input. There is one repro here and you could construct many more. Notably,
DacError
uses theEX_THROW
macro, which seems to leak 12 bytes of memory because it allocates the exception object withnew
(?!).The text was updated successfully, but these errors were encountered: