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

On close Memory Leak #98

Open
gabrielbiga opened this issue Oct 28, 2015 · 0 comments
Open

On close Memory Leak #98

gabrielbiga opened this issue Oct 28, 2015 · 0 comments

Comments

@gabrielbiga
Copy link
Contributor

Hello all.

I having trouble with this memory leak at the end of program.

==6985==
==6985== HEAP SUMMARY:
==6985==     in use at exit: 78,592 bytes in 2 blocks
==6985==   total heap usage: 744 allocs, 742 frees, 446,754 bytes allocat
==6985==
==6985== 4,864 bytes in 1 blocks are definitely lost in loss record 1 of
==6985==    at 0x4C29158: operator new(unsigned long) (in /usr/lib64/valgnd/vgpreload_memcheck-amd64-linux.so)
==6985==    by 0x510BD81: crow::Server<crow::Crow<middleware::Auth>, crowSocketAdaptor, middleware::Auth>::do_accept() (http_server.h:146)
==6985==    by 0x510B418: crow::Server<crow::Crow<middleware::Auth>, crowSocketAdaptor, middleware::Auth>::run() (http_server.h:118)
==6985==    by 0x5107E77: crow::Crow<middleware::Auth>::run() (crow.h:100
==6985==    by 0x5107AAC: server::startServer() (server.cpp:47)
==6985==    by 0x401663: main (main.cpp:49)
==6985==
==6985== LEAK SUMMARY:
==6985==    definitely lost: 4,864 bytes in 1 blocks
==6985==    indirectly lost: 0 bytes in 0 blocks
==6985==      possibly lost: 0 bytes in 0 blocks
==6985==    still reachable: 73,728 bytes in 1 blocks
==6985==         suppressed: 0 bytes in 0 blocks
==6985== Reachable blocks (those to which a pointer was found) are not shn.
==6985== To see them, rerun with: --leak-check=full --show-leak-kinds=all
==6985==
==6985== For counts of detected and suppressed errors, rerun with: -v
==6985== ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 0 from 0)

Anyone is having this problem too?

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

1 participant