Skip to content

Channel send leaks memory #116

New issue

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

Sign up for GitHub

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

Already on GitHub? Sign in to your account

Jump to bottom
Closed
jyasskin opened this issue Jul 17, 2010 · 1 comment
Closed

Channel send leaks memory #116

jyasskin opened this issue Jul 17, 2010 · 1 comment

Comments

@jyasskin
Copy link
Contributor 

io fn main() {
  let port[int] p = port();
  auto c = chan(p);
  c <| 3;
}

fails at runtime with:

rt: fatal, 'leaked memory in rust main loop (5 objects)' failed, rt/rust.cpp:33

Commenting out the send and "io" removes the leak.
@jyasskin
Copy link
Contributor Author

This appears fixed. Thanks. :)

@evanmcc evanmcc mentioned this issue Apr 3, 2012
Closed
@pcwalton pcwalton mentioned this issue Aug 13, 2014
Merged
pcwalton added a commit to pcwalton/rust that referenced this issue Aug 17, 2014
@pcwalton
librustc: Forbid external crates, imports, and/or items from being
f3bd29a 
declared with the same name in the same scope.

This breaks several common patterns. First are unused imports:

    use foo::bar;
    use baz::bar;

Change this code to the following:

    use baz::bar;

Second, this patch breaks globs that import names that are shadowed by
subsequent imports. For example:

    use foo::*; // including `bar`
    use baz::bar;

Change this code to remove the glob:

    use foo::{boo, quux};
    use baz::bar;

Or qualify all uses of `bar`:

    use foo::{boo, quux};
    use baz;

    ... baz::bar ...

Finally, this patch breaks code that, at top level, explicitly imports
`std` and doesn't disable the prelude.

    extern crate std;

Because the prelude imports `std` implicitly, there is no need to
explicitly import it; just remove such directives.

The old behavior can be opted into via the `import_shadowing` feature
gate. Use of this feature gate is discouraged.

This implements RFC rust-lang#116.

Closes rust-lang#16464.

[breaking-change]
bors added a commit that referenced this issue Aug 17, 2014
@bors
auto merge of #16482 : pcwalton/rust/resolve-shadowing, r=brson
44eca60 
declared with the same name in the same scope.

This breaks several common patterns. First are unused imports:

    use foo::bar;
    use baz::bar;

Change this code to the following:

    use baz::bar;

Second, this patch breaks globs that import names that are shadowed by
subsequent imports. For example:

    use foo::*; // including `bar`
    use baz::bar;

Change this code to remove the glob:

    use foo::{boo, quux};
    use baz::bar;

Or qualify all uses of `bar`:

    use foo::{boo, quux};
    use baz;

    ... baz::bar ...

Finally, this patch breaks code that, at top level, explicitly imports
`std` and doesn't disable the prelude.

    extern crate std;

Because the prelude imports `std` implicitly, there is no need to
explicitly import it; just remove such directives.

The old behavior can be opted into via the `import_shadowing` feature
gate. Use of this feature gate is discouraged.

This implements RFC #116.

Closes #16464.

[breaking-change]

r? @brson
pcwalton added a commit to pcwalton/rust that referenced this issue Aug 17, 2014
@pcwalton
librustc: Forbid external crates, imports, and/or items from being
7f928d1 
declared with the same name in the same scope.

This breaks several common patterns. First are unused imports:

    use foo::bar;
    use baz::bar;

Change this code to the following:

    use baz::bar;

Second, this patch breaks globs that import names that are shadowed by
subsequent imports. For example:

    use foo::*; // including `bar`
    use baz::bar;

Change this code to remove the glob:

    use foo::{boo, quux};
    use baz::bar;

Or qualify all uses of `bar`:

    use foo::{boo, quux};
    use baz;

    ... baz::bar ...

Finally, this patch breaks code that, at top level, explicitly imports
`std` and doesn't disable the prelude.

    extern crate std;

Because the prelude imports `std` implicitly, there is no need to
explicitly import it; just remove such directives.

The old behavior can be opted into via the `import_shadowing` feature
gate. Use of this feature gate is discouraged.

This implements RFC rust-lang#116.

Closes rust-lang#16464.

[breaking-change]
bors added a commit that referenced this issue Aug 17, 2014
@bors
auto merge of #16482 : pcwalton/rust/resolve-shadowing, r=brson
4a5654f 
declared with the same name in the same scope.

This breaks several common patterns. First are unused imports:

    use foo::bar;
    use baz::bar;

Change this code to the following:

    use baz::bar;

Second, this patch breaks globs that import names that are shadowed by
subsequent imports. For example:

    use foo::*; // including `bar`
    use baz::bar;

Change this code to remove the glob:

    use foo::{boo, quux};
    use baz::bar;

Or qualify all uses of `bar`:

    use foo::{boo, quux};
    use baz;

    ... baz::bar ...

Finally, this patch breaks code that, at top level, explicitly imports
`std` and doesn't disable the prelude.

    extern crate std;

Because the prelude imports `std` implicitly, there is no need to
explicitly import it; just remove such directives.

The old behavior can be opted into via the `import_shadowing` feature
gate. Use of this feature gate is discouraged.

This implements RFC #116.

Closes #16464.

[breaking-change]

r? @brson
oli-obk pushed a commit to oli-obk/rust that referenced this issue Jul 19, 2017
@solson
Merge pull request rust-lang#116 from oli-obk/master
14f094f 
fix drop impls for clike enums
kazcw pushed a commit to kazcw/rust that referenced this issue Oct 23, 2018
@pythoneer @alexcrichton
Sse2 (rust-lang#116)
3e83d38 
* added _mm_cvtsd_si64

* added _mm_cvttsd_si64; target_arch to _mm_cvtsd_si64 test
dlrobertson pushed a commit to dlrobertson/rust that referenced this issue Nov 29, 2018
@Havvy
Merge pull request rust-lang#116 from leodasvacas/remove-str-eq-example
d02c02b 
Remove example mentioning str_eq lang item
rchaser53 pushed a commit to rchaser53/rust that referenced this issue Jan 19, 2019
@mark-i-m
reword HIR intro. Fix rust-lang#116
359e814
eddyb pushed a commit to eddyb/rust that referenced this issue Jun 30, 2020
@Manishearth
Merge pull request rust-lang#116 from JohnTitor/rustup
3122410 
Rustup to the latest nightly
Aaron1011 pushed a commit to Aaron1011/rust that referenced this issue Oct 26, 2020
@dependabot
Merge pull request rust-lang#116 from bjorn3/dependabot/cargo/craneli…
06d3693 
…ft-138b2ce
@Amanieu Amanieu mentioned this issue Jun 12, 2023
Open
celinval pushed a commit to celinval/rust-dev that referenced this issue Jun 4, 2024
@danielsn @tedinski
Refactor: cleanup hooks.rs (rust-lang#116)
51653b1
celinval pushed a commit to celinval/rust-dev that referenced this issue Nov 20, 2024
@danielhumanmod
Contracts & Harnesses for Reference Conversion APIs at std::NonNull (r…
922c51a 
…ust-lang#116)

Description:
This PR introduces function contracts and proof harness for the NonNull
pointer in the Rust core library. Specifically, it verifies reference
conversion APIs, covering:

- NonNull<T>::as_mut<'a>
- NonNull<T>::as_ref<'a>
- NonNull<T>::as_uninit_mut<'a>
- NonNull<T>::as_uninit_ref<'a>
- NonNull<T>::as_uninit_slice<'a>
- NonNull<T>::as_uninit_slice_mut<'a>
- NonNull<T>::get_unchecked_mut<I>


Proof harness:

- non_null_check_as_mut
- non_null_check_as_ref
- non_null_check_as_uninit_mut
- non_null_check_as_as_uninit_ref
- non_null_check_as_as_uninit_slice
- non_null_check_as_uninit_slice_mut
- non_null_check_as_get_unchecked_mut

Towards model-checking#53

By submitting this pull request, I confirm that my contribution is made
under the terms of the Apache 2.0 and MIT licenses.
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@jyasskin