Valgrind : Leak Check / DRD : PublisherSubscriberTest possible memleak
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 35/100
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
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
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from eclipse-uprotocol/up-cpp
-
Difficulty 2/5 1-3 hours Newbie friendliness 50/100
eclipse-uprotocol/up-cpp#327 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 30/100
eclipse-uprotocol/up-cpp#320 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
eclipse-uprotocol/up-cpp#319 ·
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
eclipse-uprotocol/up-cpp#303 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
eclipse-uprotocol/up-cpp#302 ·
All issues in eclipse-uprotocol/up-cpp
Similar issues
-
Status: Awaiting triage
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
espressif/arduino-esp32#12984 ·
Maintainers usually reply within 1 day
-
torch_ops/logprob.cu does not compile with the serving container's nvcc (13.3.73); check_torch_ops.py cannot run as shippedPossibly taken A pull request linked to this issue is open or already merged. Open
Difficulty 2/5 Under an hour Newbie friendliness 72/100
ashhart/TensorFold#535 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
agent:Windows bug
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
Maintainers usually reply within 1 day