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
VM SegFault when sending Type object that doesn't exist in receiver isolate. #15983
Comments
We on the pub team (and our users) would really like this fixed; it makes debugging issues when isolates are involved much harder than it needs to be. I thought there was already a bug for this, but I can't find it now. |
This affects an open-source contributor trying to add functionality to Stagehand: https://github.com/google/stagehand/issues/192#issuecomment-74385551 |
This is a duplicate of https://code.google.com/p/dart/issues/detail?id=21398 Invalid argument(s): Illegal argument in isolate message : (object is a regular Dart Instance) The bug that nweiz is referring to is https://code.google.com/p/dart/issues/detail?id=12435. I will make it a duplicate of this bug. |
Issue #12435 has been merged into this issue. |
Added Fixed label. |
Example code:
minicrash.dart:
import "dart:isolate";
main() {
Isolate.spawnUri("minicrash-lib.dart", null, new ReceivePort().sendPort);
}
minicrash-lib.dart:
import "dart:isolate";
class C {}
main(_, p) { p.send(C); }
The result is a segmentation fault on the release VM.
On the debug VM, it prints:
runtime/vm/snapshot.cc:206: error: expected: !library_.IsNull()
Aborted (core dumped)
The text was updated successfully, but these errors were encountered: