Consider a way of not sending large strings

The Dart VM treats Strings as objects with an identifier. Chrome does not. So for strings we create an identifier which is just the entire string with a prefix. This makes it rather silly to send portions of a string across the VM protocol, but we can do it anyway for compatibility. The alternative would be to synthesize an ID and keep a map on the JS side, but this will almost certainly leak memory, and since we want this for large strings it might actually be significant. But it's an optimization to consider.

Read the issue's description of Dart VM and Chrome string handling, then trace how large strings cross the VM protocol. The issue names no files, entry points, or tests; done would require an agreed compatibility-preserving approach that avoids significant memory leakage.

Written by the indexing model from the issue text.