Possible memory leak? about rust-ctrlc HOT 1 CLOSED

Hi.
This is due to a thread CtrlC uses internally, which isn't joined, as it lasts the lifetime of the program.
The leak can be reproduced with

fn main() {
    std::thread::spawn(|| {});
}

And fixed with

fn main() {
    let t = std::thread::spawn(|| {});
    t.join().unwrap()
}

So yes, CtrlC "leaks" the thread handle and corresponding data, but as it would not have been freed anyway until the program exits, it isn't a leak that matters. set_handler can only be called once, so there's no way to leak multiple of these, thus the memory consumption is constant.

from rust-ctrlc.