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

Valgrind : Leak Check / DRD : PublisherSubscriberTest possible memleak

Open
#283 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
Mostly clear
Activity status
Stale
Tech stack
cpp
Domain
testing

Research direction

Run lint/valgrind.sh build/Release/bin/PublisherSubscriberTest and capture the detailed Valgrind or DRD contexts, not only the summary. Trace the reported allocations through PublisherSubscriberTest and related ownership paths; done means the test completes without the reported leak or threading errors.

Written by the indexing model from the issue text.

Description

quality

To reproduce locally:

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

==145606== LEAK SUMMARY:
==145606==    definitely lost: 0 bytes in 0 blocks
==145606==    indirectly lost: 0 bytes in 0 blocks
==145606==      possibly lost: 411 bytes in 13 blocks
==145606==    still reachable: 33,135 bytes in 423 blocks
==145606==         suppressed: 0 bytes in 0 blocks
==145606== 
==145606== For lists of detected and suppressed errors, rerun with: -s
==145606== ERROR SUMMARY: 4 errors from 4 contexts (suppressed: 0 from 0)
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.