ci builds: drop macOS leak detection#4859
Conversation
Memory leak detection using the leaks application on macOS is brittle - IIRC, it tries to background itself, but keeps a file descriptor open. I previously got this to the point where it would exit cleanly (instead of refusing to exit, and causing a build timeout after 60 minutes). But apparently these mechanations obscure clar's error code. Disable leak detection on macOS until we can resolve this problem.
|
lol, for once, the macOS build completes first! Obviously, correctness and reproducibility are the most important things here. But I do want to make sure that we're doing leak detection on all our builds, so I'll revisit this and get it enabled again. @tiennou, do you happen to know if |
|
Yeah, leaks is slightly painful, but as far as I know the only tool that does this, and last I checked A few notes :
My current (out of habit) usage is to set a breakpoint on clar's last return statement, and run |
|
#4860 is an obvious improvement. |
Memory leak detection using the leaks application on macOS is brittle -
IIRC, it tries to background itself, but keeps a file descriptor open.
I previously got this to the point where it would exit cleanly (instead
of refusing to exit, and causing a build timeout after 60 minutes). But
apparently these mechanations obscure clar's error code.
Disable leak detection on macOS until we can resolve this problem.