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

Investigate potential memory leaks #1095

Open
luciansmith opened this issue Apr 13, 2023 · 0 comments
Open

Investigate potential memory leaks #1095

luciansmith opened this issue Apr 13, 2023 · 0 comments
Labels

Comments

@luciansmith
Copy link

Using 'Deleaker' on Windows claims that the following code leaks memory a lot:

C:\Users\Lucian\Desktop\roadrunner\source\llvm\MCJit.cpp, line 92
C:\Users\Lucian\Desktop\roadrunner\source\llvm\MCJit.cpp, line 93
C:\Users\Lucian\Desktop\roadrunner\source\llvm\MCJit.cpp, line 127
C:\Users\Lucian\Desktop\roadrunner\source\llvm\MCJit.cpp, line 232
C:\Users\Lucian\Desktop\roadrunner\source\llvm\Jit.cpp, line 38

Also:
C:\Users\Lucian\Desktop\roadrunner\source\conservation\ConservationExtension.cpp, line 342
C:\Users\Lucian\Desktop\roadrunner\source\CVODEIntegrator.cpp, line 698

There's a lot more, but most are duplicates of those, in various contexts (running test_sundials_cvode_integration).

It might be easiest to tackle this with valgrind on ubuntu?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant