-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
Comments
The check seems to fail at an 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
however commissioning generally looks ok. Could you check which pool gets this? At least that should narrow down figuring out what object leaks. |
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) |
@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? |
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.
The text was updated successfully, but these errors were encountered: