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 Leak #12

Open
CoderHam opened this issue Jul 29, 2020 · 1 comment
Open

Memory Leak #12

CoderHam opened this issue Jul 29, 2020 · 1 comment

Comments

@CoderHam
Copy link

Is there a known memory leak in cmem?
I found this in the logs from valgrind.

==1049== HEAP SUMMARY:
==1049==     in use at exit: 1,349,153,600 bytes in 1,333,650 blocks
==1049==   total heap usage: 2,621,433 allocs, 1,287,783 frees, 2,955,906,430 bytes allocated
==1049==
==1049== 32 bytes in 1 blocks are definitely lost in loss record 85,881 of 182,145
==1049==    at 0x4C3017F: operator new(unsigned long) (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
==1049==    by 0x5C56659: cnmem::Manager::allocateBlockUnsafe(cnmem::Block*&, cnmem::Block*&, unsigned long) (in /opt/tritonserver/lib/libtritonserver.so)
==1049==    by 0x5C57568: cnmem::Manager::reserve(unsigned long)
==1049==    by 0x5C5806B: cnmemInit
@yuxineverforever
Copy link

yuxineverforever commented Jul 29, 2020

I found this as well. @jdemouth

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

No branches or pull requests

2 participants