Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Valgrind : Leak check / DRD : NotificatoinSinkTest possible mem leak

Open
#281 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
cpp
Domain
testing-qa

Research direction

Start by running lint/valgrind.sh build/Release/bin/NotificationSinkTest and inspect the Valgrind/DRD output for the reported possibly lost blocks. Trace the test and its cleanup path from that executable; done means the check no longer reports the possible leak without introducing new failures.

Written by the indexing model from the issue text.

Description

quality

Possible mem leak

To reproduce locally:

bash lint/valgrind.sh build/Release/bin/NotificationSinkTest

==145455== LEAK SUMMARY:
==145455==    definitely lost: 0 bytes in 0 blocks
==145455==    indirectly lost: 0 bytes in 0 blocks
==145455==      possibly lost: 411 bytes in 13 blocks
==145455==    still reachable: 32,889 bytes in 420 blocks
==145455==         suppressed: 0 bytes in 0 blocks
==145455== 
Dominant language
C++
Stars
29
Forks
32
PR merge metrics
No merged PRs in 30d

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from eclipse-uprotocol/up-cpp

All issues in eclipse-uprotocol/up-cpp

Similar issues

More C++ issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.