[SERVER-22519] Expose a mechanism to check leaks on demand Created: 08/Feb/16  Updated: 15/Nov/18  Resolved: 15/Nov/18

Status: Closed
Project: Core Server
Component/s: Testing Infrastructure
Affects Version/s: 3.3.1
Fix Version/s: None

Type: Improvement Priority: Major - P3
Reporter: Robert Guo (Inactive) Assignee: DO NOT USE - Backlog - Test Infrastructure Group (TIG)
Resolution: Won't Fix Votes: 0
Labels: close
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
Participants:
Linked BF Score: 0

 Description   

Introduce a command or something to that effect which can check for leaks on demand.

lsan provides int __lsan_do_recoverable_leak_check(); which could be leveraged for this purpose.

This would improve the debuggability of long running tests, such as the fuzzer or the longevity suite.



 Comments   
Comment by Mira Carey [ 08/Feb/16 ]

Note that we have some areas of the subsystem that will erroneously produces leaks (the js framework in particular) due to asan's inability to verify ownership that's been passed to another thread. Not sure if you'll run into it, but this may be trickier than you'd expect.

Generated at Thu Feb 08 04:00:38 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.