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 in retrieve_sensors() #105

Closed
dgraziotin opened this issue Apr 2, 2017 · 0 comments
Closed

Memory leak in retrieve_sensors() #105

dgraziotin opened this issue Apr 2, 2017 · 0 comments

Comments

@dgraziotin
Copy link
Collaborator

As reported by valgrind

==30820== 
==30820== HEAP SUMMARY:
==30820==     in use at exit: 51 bytes in 1 blocks
==30820==   total heap usage: 305 allocs, 304 frees, 525,754 bytes allocated
==30820== 
==30820== 51 bytes in 1 blocks are definitely lost in loss record 1 of 1
==30820==    at 0x4C2CB3F: malloc (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
==30820==    by 0x10B17C: retrieve_sensors (mbpfan.c:150)
==30820==    by 0x10BD47: mbpfan (mbpfan.c:513)
==30820==    by 0x10ADEC: go_daemon (daemon.c:225)
==30820==    by 0x10C478: main (main.c:148)
==30820== 
==30820== LEAK SUMMARY:
==30820==    definitely lost: 51 bytes in 1 blocks
==30820==    indirectly lost: 0 bytes in 0 blocks
==30820==      possibly lost: 0 bytes in 0 blocks
==30820==    still reachable: 0 bytes in 0 blocks
==30820==         suppressed: 0 bytes in 0 blocks
==30820== 
==30820== For counts of detected and suppressed errors, rerun with: -v
==30820== ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 0 from 0)

path_begin needs to be free'd up

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