Skip to content

Flaky flutter engine test crashes in PushBackdropFilterToVisitedPlatformViews #121096

@mkustermann

Description

@mkustermann

We are seeing some seemingly flaky engine test crashes on Dart CI (flutter head-head-head bot), see log:

[ERROR:flutter/fml/backtrace.cc(108)] Caught signal SIGSEGV during program execution.
Frame 0: 0x55fed63eb2ba flutter::testing::ShellTest_PushBackdropFilterToVisitedPlatformViews_Test::TestBody()
Frame 1: 0x55fed90dc00b testing::internal::HandleSehExceptionsInMethodIfSupported<>()
Frame 2: 0x55fed90cefc7 testing::internal::HandleExceptionsInMethodIfSupported<>()
Frame 3: 0x55fed90be663 testing::Test::Run()
Frame 4: 0x55fed90bed24 testing::TestInfo::Run()
Frame 5: 0x55fed90bf32d testing::TestSuite::Run()
Frame 6: 0x55fed90c8ad1 testing::internal::UnitTestImpl::RunAllTests()
Frame 7: 0x55fed90df18b testing::internal::HandleSehExceptionsInMethodIfSupported<>()
Frame 8: 0x55fed90d0937 testing::internal::HandleExceptionsInMethodIfSupported<>()
Frame 9: 0x55fed90c86cf testing::UnitTest::Run()
Frame 10: 0x55fed856f7f1 RUN_ALL_TESTS()
Frame 11: 0x55fed856f5d2 main
Frame 12: 0x7ff3ec2fec87 __libc_start_main
Frame 13: 0x55fed628fbaa _start

Seems unrelated to Dart, @zanderso maybe someone from engine team can investigate?

Metadata

Metadata

Assignees

No one assigned

    Labels

    P2Important issues not at the top of the work lista: tests"flutter test", flutter_test, or one of our testsc: contributor-productivityTeam-specific productivity, code health, technical debt.c: crashStack traces logged to the consolec: flakeTests that sometimes, but not always, incorrectly passengineflutter/engine related. See also e: labels.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions