Skip to content

Force a GC right prior to task death. #156

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
froystig opened this issue Aug 27, 2010 · 2 comments
Closed

Force a GC right prior to task death. #156

froystig opened this issue Aug 27, 2010 · 2 comments
Labels
A-runtime Area: std's runtime and "pre-main" init for handling backtraces, unwinds, stack overflows E-easy Call for participation: Easy difficulty. Experience needed to fix: Not much. Good first issue.

Comments

@froystig
Copy link
Contributor

To prevent the task from leaking memory, we ought to GC one last time before task death.
@pcwalton pcwalton reopened this Jun 29, 2011
@pcwalton
Copy link
Contributor

Oops, wrong bug number

@graydon
Copy link
Contributor

graydon commented Jul 25, 2012

I believe this is sufficiently meaningless in the current regime as to be worth closing. The task-local heap will be freed entirely and the exchange heap references will be freed while unwinding.

@graydon graydon closed this as completed Jul 25, 2012
oli-obk pushed a commit to oli-obk/rust that referenced this issue Jul 19, 2017
@eddyb
Merge pull request rust-lang#156 from oli-obk/master
9a32772 
Use rustc generated shims instead of interpreter hacks
keeperofdakeys pushed a commit to keeperofdakeys/rust that referenced this issue Dec 12, 2017
Fixes rust-lang#156
e95c53d
keeperofdakeys pushed a commit to keeperofdakeys/rust that referenced this issue Dec 12, 2017
@alexcrichton
Merge pull request rust-lang#157 from dhuseby/fixing_bsd_ncpu
f9073f4 
Fixes rust-lang#156
kazcw pushed a commit to kazcw/rust that referenced this issue Oct 23, 2018
@hdevalence @alexcrichton
avx2: add _mm256_shuffle_epi32 reusing _mm_shuffle_epi32 code (rust-l…
87fec0f 
…ang#156)
dlrobertson pushed a commit to dlrobertson/rust that referenced this issue Nov 29, 2018
@steveklabnik
Merge pull request rust-lang#156 from Havvy/reprs
d812ea2 
New Section - Type Layout
Aaron1011 pushed a commit to Aaron1011/rust that referenced this issue Oct 26, 2020
@bjorn3
Merge pull request rust-lang#156 from bjorn3/dependabot/cargo/craneli…
cf287e3 
…ft-af045c1

Bump cranelift from `606eee5` to `af045c1`
djtech-dev pushed a commit to djtech-dev/rust that referenced this issue Dec 9, 2021
@TheDan64
Made build_struct_gep safe. Fixes rust-lang#156
0dc6e72
antoyo added a commit to antoyo/rust that referenced this issue Jun 7, 2022
@antoyo
Merge pull request rust-lang#156 from yvt/fix-int-ops
d69ada6 
Implement `saturating_{add, sub}` for non-native integer types
celinval pushed a commit to celinval/rust-dev that referenced this issue Nov 20, 2024
@QinyuanWu @zhassan-aws
Contracts & Harnesses for NonNull::read, NonNull::read_volatile, …
94a31f5 
…`NonNull::read_unaligned` (rust-lang#156)

Towards rust-lang#52 

Contracts & Harnesses for `NonNull::read`, `NonNull::read_volatile`,
`NonNull::read_unaligned`
### Discussion
For the ensures clause in the contract for `NonNull::read`, I could not
directly compare the value pointed by self and result due to unsized and
lack of PartialEq implementation, and the comparison is currently moved
to the harness.
### Verification
Successful verification:
```
SUMMARY:
 ** 0 of 141 failed

VERIFICATION:- SUCCESSFUL
Verification Time: 0.1760525s

Complete - 5 successfully verified harnesses, 0 failures, 5 total.
```

By submitting this pull request, I confirm that my contribution is made
under the terms of the Apache 2.0 and MIT licenses.

---------

Co-authored-by: Zyad Hassan <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
A-runtime Area: std's runtime and "pre-main" init for handling backtraces, unwinds, stack overflows E-easy Call for participation: Easy difficulty. Experience needed to fix: Not much. Good first issue.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@graydon @froystig @pcwalton