Skip to content

Ensure that all ReceivePorts in pub are closed when they're finished #14724

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.

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

Closed
nex3 opened this issue Nov 1, 2013 · 5 comments
Closed

Ensure that all ReceivePorts in pub are closed when they're finished #14724

nex3 opened this issue Nov 1, 2013 · 5 comments
Labels
closed-obsolete Closed as the reported issue is no longer relevant P3 A lower priority bug or feature request

Comments

@nex3
Copy link
Member

nex3 commented Nov 1, 2013

Isolate ReceivePorts are no longer automatically garbage collected, so we need to be sure we're closing them properly so we don't leak memory.

@nex3
Copy link
Member Author

nex3 commented Nov 1, 2013

Marked this as blocking #13848.

@munificent
Copy link
Member

Removed Priority-Unassigned label.
Added Priority-Low label.

@munificent
Copy link
Member

Do we have a way to validate this? Do we know if it's still an issue?

@nex3
Copy link
Member Author

nex3 commented Jun 17, 2014

I think we'd have seen some effects if this were an issue.


Added AssumedStale label.

@nex3 nex3 added Type-Defect P3 A lower priority bug or feature request closed-obsolete Closed as the reported issue is no longer relevant labels Jun 17, 2014
@DartBot
Copy link

DartBot commented Jun 5, 2015

This issue has been moved to dart-lang/pub#699.

This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
closed-obsolete Closed as the reported issue is no longer relevant P3 A lower priority bug or feature request
Projects
None yet
Development

No branches or pull requests

3 participants