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

[SVE1] Possible memory leak in chip-tool #20608

Closed
doru91 opened this issue Jul 12, 2022 · 3 comments · Fixed by #20727
Closed

[SVE1] Possible memory leak in chip-tool #20608

doru91 opened this issue Jul 12, 2022 · 3 comments · Fixed by #20727
Labels
leak Memory leak bug memory V1.0

Comments

@doru91
Copy link
Contributor

doru91 commented Jul 12, 2022

Problem

After successfully commissioning with the 4th administrator, chip-tool reports:

[1657625195.034286][3459:3459] CHIP:SPT: VerifyOrDie failure at ../../examples/chip-tool/third_party/connectedhomeip/src/lib/support/Pool.h:317: Allocated() == 0

This is 100% reproductible on NXP platform.
chip_tool_logs_4th_admin.txt
dut_logs_4th_admin.txt

Also attached the entire logs on the DUT and chip-tool side.

@andy31415
Copy link
Contributor

The check seems to fail at an assert all memory has been freed by the time Pool is deallocated, so we seem to leak a pool object.

Maybe we could compare logs from the 1,2,3 logs and the 4th one. My guess is that some error condition does not fee up its data. Looking at errors I see

[1657625194.992609][3459:3464] CHIP:EM: OnMessageReceived failed, err = ../../examples/chip-tool/third_party/connectedhomeip/src/me                           ssaging/ExchangeMgr.cpp:274: CHIP Error 0x00000070: Unsolicited msg with originator bit clear

however commissioning generally looks ok.

Could you check which pool gets this? At least that should narrow down figuring out what object leaks.

@andy31415
Copy link
Contributor

Removed cert blocker: memory leaks are likely not cert blockers.

Or if they are, please add a justification (like cert test does the 4 executions and because app crashes, certification fails)

@andy31415
Copy link
Contributor

@cjandhyala - please see above: is this actually a cert blocker (if so please explain and re-add the tag) or was my removal of cert blocker tag correct?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
leak Memory leak bug memory V1.0
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants