You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
area-vmUse area-vm for VM related issues, including code coverage, and the AOT and JIT backends.gardeningtype-bugIncorrect behavior (everything from a crash to more subtle misbehavior)type-test
This failure currently affects a large number of bots:
Unhandled exception:
Out of Memory
#0 _StringBase._concatRangeNative (dart:core-patch/string_patch.dart:956:34)
#1 String._concatAll (dart:core-patch/string_patch.dart:1008:26)
#2 _StringBase._interpolate (dart:core-patch/string_patch.dart:876:27)
#3 main (file:///b/s/w/ir/tests/standalone/string_overflow_test.dart:14:34)
#4 _delayEntrypointInvocation.<anonymous closure> (dart:isolate-patch/isolate_patch.dart:283:19)
#5 _RawReceivePortImpl._handleMessage (dart:isolate-patch/isolate_patch.dart:184:12)
The reason this old test is failing now is that 201227 renamed the file which likely caused it to start getting picked up as a test. Plus the catch for OoM errors was removed.
I'll go ahead and approve this failing to unblock the bots.
Though my personal feeling is that this test probably should be rewritten to at least be less wasteful with memory, if possible.
The text was updated successfully, but these errors were encountered:
The test standalone/string_overflow_test.dart is causing crashes
and out-of-memory thrashing on some configurations. It was originally
a regression test that concatenating a string with 2^31 characters
did not overflow a 32-bit signed integer.
It was changed to exponentially grow a string until an out-of-memory
runtime exception is thrown in Dart. On some VM configurations,
this crashes the machine instead.
Restoring it to only check concatenating a string of 2^31 bytes.
Bug: #46225
Change-Id: Ib50625fe14be2613c907a7bc30cd57766693f6aa
Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/332423
Reviewed-by: Martin Kustermann <kustermann@google.com>
area-vmUse area-vm for VM related issues, including code coverage, and the AOT and JIT backends.gardeningtype-bugIncorrect behavior (everything from a crash to more subtle misbehavior)type-test
This failure currently affects a large number of bots:
The reason this old test is failing now is that 201227 renamed the file which likely caused it to start getting picked up as a test. Plus the catch for OoM errors was removed.
I'll go ahead and approve this failing to unblock the bots.
Though my personal feeling is that this test probably should be rewritten to at least be less wasteful with memory, if possible.
The text was updated successfully, but these errors were encountered: