Repository navigation
Dart VM crash during web framework tests in Engine CI #97381
Description
On the Dart SDK roll here: flutter-team-archive/engine#31106
../../runtime/vm/object.cc: 4429: error: Unable to use class 47441055083116 which is not loaded yet.
version=2.17.0-54.0.dev (dev) (Mon Jan 24 15:02:20 2022 -0800) on "linux_x64"
pid=15784, thread=15848, isolate_group=main(0x564b788d9000), isolate=main(0x564b788da800)
isolate_instructions=564b76043ac0, vm_instructions=564b76043ac0
pc 0x0000564b762ae0dc fp 0x00007f5520cfdf60 dart::Profiler::DumpStackTrace(void*)+0x7c
pc 0x0000564b76043c74 fp 0x00007f5520cfe040 dart::Assert::Fail(char const*, ...) const+0x84
pc 0x0000564b762420ac fp 0x00007f5520cfe060 /b/s/w/ir/x/w/flutter/bin/cache/dart-sdk/bin/dart+0x20740ac
pc 0x0000564b761b3be3 fp 0x00007f5520cfe180 dart::ClassFinalizer::LoadClassMembers(dart::Class const&)+0xd3
pc 0x0000564b76239b53 fp 0x00007f5520cfe1d0 dart::Class::EnsureIsFinalized(dart::Thread*) const+0xc3
pc 0x0000564b762fe30f fp 0x00007f5520cfe230 dart::PatchableCallHandler::ResolveTargetFunction(dart::Object const&)+0x16f
pc 0x0000564b762fe420 fp 0x00007f5520cfe2a0 dart::PatchableCallHandler::ResolveSwitchAndReturn(dart::Object const&)+0x20
pc 0x0000564b762ff059 fp 0x00007f5520cfe4c0 dart::DRT_SwitchableCallMiss(dart::NativeArguments)+0x2d9
...
Command and full backtrace in:
https://ci.chromium.org/ui/p/flutter/builders/prod/Linux%20SDK%20Drone/104340/overview
Marking P2 for investigation. Will bump up or down depending on whether this repeats on Engine CI rebuilds.
Activity
a-siva commentedon Jan 27, 2022
/cc @alexmarkov
alexmarkov commentedon Jan 27, 2022
I tried running the tests locally a few times, but the crash doesn't appear.
@zanderso Is there a core dump for this crash?
zanderso commentedon Jan 28, 2022
I believe we don't collect core files from these runs. @jason-simmons to confirm.
jason-simmons commentedon Jan 28, 2022
No - we don't have a core dump from this test
zanderso commentedon Feb 2, 2022
To clarify, it's unlikely that that Dart roll introduced the flake. The roll only had some dead code removal and an analysis server change in it. It was a coincidence that the VM happened to crash on that Dart -> Engine roll.
a-siva commentedon Feb 4, 2022
Considering that the crash is not easily reproducible, could we lower the priority of this issue.
zanderso commentedon Feb 4, 2022
Yeah, I haven't seen this come up again, so dropping to P4.
nshahan commentedon Feb 13, 2026
@mdebbar
The stack traces look like a VM issue, not the web. Do you want to triage somewhere else?
zanderso commentedon Feb 13, 2026
This issue seems stale (from 2022). I'm just going to close it. If the Flutter gardening rotation starts seeing it again, we can open a new issue.
github-actions commentedon Feb 27, 2026
This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of
flutter doctor -vand a minimal reproduction of the issue.