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.

Sign up for GitHub

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

Jump to bottom

Java test Run Pairing Onnetwork and get diagnostic log Test is flaky #36734

Open
andy31415 opened this issue Dec 5, 2024 · 0 comments · May be fixed by #36742
Open

Java test Run Pairing Onnetwork and get diagnostic log Test is flaky #36734

andy31415 opened this issue Dec 5, 2024 · 0 comments · May be fixed by #36742
Assignees
@joonhaengHeo

Comments

@andy31415
Copy link
Contributor

After #36591 we seem to have frequent errors in diagnostics log test. One such instance reports:

2024-12-05T05:59:48.0688225Z [2024-12-05 05:59:48.068222][�[32mAPP �[0m][�[33mSTDOUT�[0m][18779:18779] CHIP:EM: ExchangeContext: 48186i delegate=null
2024-12-05T05:59:48.0689511Z [2024-12-05 05:59:48.068228][�[32mAPP �[0m][�[33mSTDOUT�[0m][18779:18779] CHIP:SPT: VerifyOrDie failure at src/lib/support/Pool.h:405: Allocated() == 0

I believe it may be some race issue here where we stop the application before some pool (unclear which pool) frees its objects.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@joonhaengHeo joonhaengHeo

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

[Android] Fix memory leakage in AndroidLogDownloadFromNode Class joonhaengHeo/connectedhomeip
2 participants
@andy31415 @joonhaengHeo