Skip to content

main libuv event loop leaks memory on mac #8253

New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Closed
brson opened this issue Aug 3, 2013 · 1 comment
Closed

main libuv event loop leaks memory on mac #8253

brson opened this issue Aug 3, 2013 · 1 comment
Labels
A-runtime Area: std's runtime and "pre-main" init for handling backtraces, unwinds, stack overflows

Comments

@brson
Copy link
Contributor

brson commented Aug 3, 2013

I suspect it's a race between process exit and the termination of worker threads, and thus not a serious problem, but it should probably be investigated. For now I'm going to add a valgrind suppression.

bors added a commit that referenced this issue Aug 4, 2013
I suspect that this is a race between process exit and the termination of
worker threads used by libuv (if I sleep before exit it doesn't leak). This
isn't going to cause any real problems but should probably be fixed at
some point.

r? @pcwalton

cc #8253
bors added a commit that referenced this issue Aug 27, 2013
This callstack changed when the FFI did. I am still a little frightened by
this suppression.

cc #8253
@flaper87
Copy link
Contributor

flaper87 commented Feb 5, 2014

As per discussion on IRC, this bug is seems to be old. Several iterations have been done over this.

@flaper87 flaper87 closed this as completed Feb 5, 2014
flip1995 pushed a commit to flip1995/rust that referenced this issue Feb 26, 2022
Add `print_in_format_impl` lint

changelog: new lint: [`print_in_format_impl`]

Lints the use of `print`-like macros in manual `Display`/`Debug` impls. I feel like I make this mistake every time I write one 😄

r? `@camsteffen`
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
A-runtime Area: std's runtime and "pre-main" init for handling backtraces, unwinds, stack overflows
Projects
None yet
Development

No branches or pull requests

2 participants