fnotifystat: memory leak when filtering file paths
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Fnotifystat |
Fix Released
|
Medium
|
Colin Ian King | ||
Bug Description
valgrind is showing a memory leak:
==390==
==390== HEAP SUMMARY:
==390== in use at exit: 94,772 bytes in 3,268 blocks
==390== total heap usage: 4,311 allocs, 1,043 frees, 177,825 bytes allocated
==390==
==390== LEAK SUMMARY:
==390== definitely lost: 94,772 bytes in 3,268 blocks
==390== indirectly lost: 0 bytes in 0 blocks
==390== possibly lost: 0 bytes in 0 blocks
==390== still reachable: 0 bytes in 0 blocks
==390== suppressed: 0 bytes in 0 blocks
==390== Rerun with --leak-check=full to see details of leaked memory
==390==
==390== For counts of detected and suppressed errors, rerun with: -v
==390== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0)
this occurs because the filtering check returns before freeing the gathered filename
Related branches
| Changed in fnotifystat: | |
| status: | New → In Progress |
| importance: | Undecided → Medium |
| assignee: | nobody → Colin Ian King (colin-king) |
| Colin Ian King (colin-king) wrote | #1 |
| Changed in fnotifystat: | |
| status: | In Progress → Fix Committed |
| Changed in fnotifystat: | |
| status: | Fix Committed → Fix Released |
Fix committed, commit http://