Open dcharkes opened 4 years ago
Does not seem to be FFI specific at all based on the stack trace.
/cc @mkustermann
N.b. this failure was approved by someone - I only noticed this while running all tests locally with test.py (instead of test.dart).
For triaging it might me worthwhile querying the results database about when this started failing.
The FFI tries to allocate an object in a no-safepoint-scope on arm64. (The test does not fail on other architectures.)
The test that triggers this passes a null to trigger an exception in the trampoline.