serai-node --network solo --identity alice, when allowed to start producing blocks and then killed after another minute, reports ~6 KB of leaks.
These aren't inherently an issue if they're finite. It just means someone, somewhere used a core::mem::forget on a heap-allocated type to effect a static. We just have to ensure these are in fact fixed-size statics and not an actual leak which will grow over runtime.
Additionally, while our CI allows compiling with ASan, it drops the results from LeakSanitizer as those are reported on termination when the test is already completed. We should solve for a way to actually propagate the LeakSanitizer results so this is reflected in CI.
serai-node --network solo --identity alice, when allowed to start producing blocks and then killed after another minute, reports ~6 KB of leaks.These aren't inherently an issue if they're finite. It just means someone, somewhere used a
core::mem::forgeton a heap-allocated type to effect a static. We just have to ensure these are in fact fixed-size statics and not an actual leak which will grow over runtime.Additionally, while our CI allows compiling with ASan, it drops the results from LeakSanitizer as those are reported on termination when the test is already completed. We should solve for a way to actually propagate the LeakSanitizer results so this is reflected in CI.