If a protocol tree constructs more than two actors on the child side, the child process will abort with the error: ABORT: need a route: MSG_ROUTING_NONE != msg->routing_id() The reason is that MSG_ROUTING_NONE is a "special ID" with the value -2. But our actor ID assignment scheme uses negative IDs for actors created on the child side (positive for parent side). The fix is to change the way the chromium transport layer marks messages as being none/control/routed. This should be its own header field.
10 years ago
Depends on: 518126
Created attachment 402518 [details] [diff] [review] fix Waiting on test infrastructure to land before pushing. I went with a lazy fix. A "real" fix would distinguish between message routing types (none, control, routed) with a separate field.
Created attachment 404667 [details] [diff] [review] updated test case
Attachment #402517 - Attachment is obsolete: true
Status: NEW → RESOLVED
Last Resolved: 10 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.