Uh oh!
There was an error while loading.Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork1k
DotMemoryDiagnoser implementation#2549
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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
DotMemoryDiagnoser implementation#2549
Uh oh!
There was an error while loading.Please reload this page.
Conversation
martinothamar commentedMar 31, 2024
There was a segfault happening for the integration test that I don't quite understand. I can no longer reproduce it after the last commit. I tried to debug some dumps locally but was unable to find relevant exceptions, so my only guess atm is that the crash originates from unmanaged code. Since changing the init logic seemed to affect things, and the crash always happening during In any case, I would like to test out using only the JetBrains API directly |
martinothamar commentedMar 31, 2024 • edited
Loading Uh oh!
There was an error while loading.Please reload this page.
edited
Uh oh!
There was an error while loading.Please reload this page.
The last commit simplifies the implementation of the tool by using only the Jetbrains API, and the lifetime of it is more clearly managed based on the incoming signals. I'd be willing to try the same with dotTrace impl. I also want to make a flag like |
AndreyAkinshin commentedApr 1, 2024
@martinothamar thank you very much for this PR! |
Implements
DotMemoryDiagnoserto matchDotTraceDiagnoserCommonpackage or just use<Compile Include="..." />Sample output of
IntroDotMemoryDiagnoser