Skip to content

benchmark-linux-try CQ flaky due to pkg/front_end/tool/fasta_perf.dart crash in VM #38528

@sortie

Description

@sortie

The benchmark-linux-try builder in the CQ has become flaky with a VM crash when running the pkg/front_end/tool/fasta_perf.dart benchmark on linux-ia32. This builder is not subject to deflaking and this situation currently disrupts the CQ runs for all Dart developers. Since the flake first appeared, it has hit 4 of 18 benchmark-linux-try tryjobs on multiple changelists.

Example crashes:

I can reproduce the issue locally on master (f546362) on linux-ia32 by running:

cat > hello.dart << EOF                                                                                                  
main() {
  print("Hello, World");
}
EOF
while out/ReleaseIA32/dart pkg/front_end/tool/fasta_perf.dart kernel_gen_e2e hello.dart; do true; done

After 75 iterations, I managed to hit the crash locally:

===== CRASH =====
si_signo=Segmentation fault(11), si_code=2, si_addr=0xf322ce06
version=2.6.0-edge.f546362691fe17b38298e5d9baa25c0c292f5448 (Mon Sep 23 16:35:05 2019 +0200) on "linux_ia32"
thread=92201, isolate=main(0x2a8c700)
  pc 0xf322ce06 fp 0xf603e210 Unknown symbol
...
  pc 0xf7880979 fp 0xf603eef4 Unknown symbol
  pc 0x01a3417b fp 0xf603ef68 dart::DartEntry::InvokeFunction(dart::Function const&, dart::Array const&, dart::Array const&, unsigned int)
  pc 0x01a35fdd fp 0xf603efa8 dart::DartLibraryCalls::HandleMessage(dart::Object const&, dart::Instance const&)
  pc 0x01a63e20 fp 0xf603f0d8 dart::IsolateMessageHandler::HandleMessage(std::__2::unique_ptr<dart::Message, std::__2::default_delete<dart::Message> >)
  pc 0x01a88b45 fp 0xf603f128 dart::MessageHandler::HandleMessages(dart::MonitorLocker*, bool, bool)
  pc 0x01a893b1 fp 0xf603f188 dart::MessageHandler::TaskCallback()
  pc 0x01a89b07 fp 0xf603f1a8 out/ReleaseIA32/dart+0x1689b07
  pc 0x01b7a751 fp 0xf603f1e8 dart::ThreadPool::Worker::Loop()
  pc 0x01b7a5f7 fp 0xf603f218 dart::ThreadPool::Worker::Main(unsigned int)
  pc 0x01b00e84 fp 0xf603f2d8 out/ReleaseIA32/dart+0x1700e84
  pc 0xf7bbc982 fp 0xf603f3a8 /lib/i386-linux-gnu/libpthread.so.0+0x6982
-- End of DumpStackTrace
Aborted

The issue has only manifested itself in 4 of 18 tryruns since it first appeared. If that ratio is to be believed, it might affect 22% of all CQ runs.

cc @mkustermann @askeksa-google

Metadata

Metadata

Labels

P1A high priority bug; for example, a single project is unusable or has many test failuresarea-vmUse area-vm for VM related issues, including code coverage, and the AOT and JIT backends.crashProcess exits with SIGSEGV, SIGABRT, etc. An unhandled exception is not a crash.type-bugIncorrect behavior (everything from a crash to more subtle misbehavior)

Type

No type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions