Skip to content
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

Overflowing smi range for port ids with native ports #5711

Closed
madsager opened this issue Oct 8, 2012 · 3 comments
Closed

Overflowing smi range for port ids with native ports #5711

madsager opened this issue Oct 8, 2012 · 3 comments
Labels
area-vm Use area-vm for VM related issues, including code coverage, FFI, and the AOT and JIT backends.

Comments

@madsager
Copy link
Contributor

madsager commented Oct 8, 2012

In dart:io we use native ports to post data to the thread pool. We are seeing issues where we are overflowing smi range for port ids.

The scenario is:

   nativePort.call(request).transform((result) { ... });

For each call, a receive port is allocated. We perform these calls for each little chunk of file data that we process. Port ids are allocated by just incrementing a counter which is never reset. On servers that run for days and process a lot of file data, this has started overflowing smi range for the port ids.

@iposva-google
Copy link
Contributor

Removed Priority-Medium label.
Added Priority-Unassigned label.

@ricowind
Copy link
Contributor

Isn't this already fixed?

@madsager madsager added Type-Defect area-vm Use area-vm for VM related issues, including code coverage, FFI, and the AOT and JIT backends. labels Sep 25, 2013
@iposva-google
Copy link
Contributor

Stale.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area-vm Use area-vm for VM related issues, including code coverage, FFI, and the AOT and JIT backends.
Projects
None yet
Development

No branches or pull requests

4 participants