Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Memory leaks in mscordacwks #4429

Closed
goldshtn opened this issue Aug 12, 2015 · 1 comment
Closed

Memory leaks in mscordacwks #4429

goldshtn opened this issue Aug 12, 2015 · 1 comment

Comments

@goldshtn
Copy link

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 (?!).

@MattWhilden
Copy link
Contributor

Thanks for reporting the issue. Adding someone from the diagnostics team to potentially comment. @noahfalk

@tzwlai tzwlai assigned mikem8361 and unassigned noahfalk May 2, 2016
@tzwlai tzwlai assigned alsemenn and unassigned mikem8361 May 27, 2016
alsemenn referenced this issue in dotnet/coreclr Jun 9, 2016
Fix memory leak in issue #1379
@alsemenn alsemenn closed this as completed Jun 9, 2016
@msftgits msftgits transferred this issue from dotnet/coreclr Jan 30, 2020
@msftgits msftgits added this to the 1.1.x milestone Jan 30, 2020
@ghost ghost locked as resolved and limited conversation to collaborators Jan 5, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

6 participants