TestClientInput/DemoPrivateProtobuf memory leak is causing regular CI test failures
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Mir |
Fix Released
|
High
|
Daniel van Vugt | ||
mir (Ubuntu) |
Fix Released
|
High
|
Unassigned |
Bug Description
Twice now in CI I've had branches (that are far away from the input stack) fail with a memory leak reported in TestClientInput in the acceptance tests.
https:/
https:/
I have not been able to reproduce this problem locally with valgrind and this test.
update: more failures on different branches
https:/
https:/
This seems to be racy... some branches are passing and some are not
Related branches
- PS Jenkins bot (community): Approve (continuous-integration)
- Alan Griffiths: Approve
- Alexandros Frantzis (community): Approve
-
Diff: 39 lines (+16/-2)2 files modifiedsrc/client/mir_client_library.cpp (+11/-2)
tests/acceptance-tests/test_protobuf.cpp (+5/-0)
description: | updated |
description: | updated |
Changed in mir: | |
assignee: | nobody → Daniel van Vugt (vanvugt) |
status: | Confirmed → In Progress |
summary: |
- TestClientInput memory leak in CI + TestClientInput memory leak is causing regular CI test failures |
summary: |
- TestClientInput memory leak is causing regular CI test failures + TestClientInput/DemoPrivateProtobuf memory leak is causing regular CI + test failures |
Changed in mir: | |
importance: | Medium → High |
Changed in mir: | |
status: | Fix Committed → Fix Released |
Changed in mir (Ubuntu): | |
status: | New → Triaged |
importance: | Undecided → High |
Other sporadic CI test failures in the past have hinted that there are races in the input system/tests. Should be easy to discover with: valgrind --tool=helgrind