Skip to content

Engine roll causing observatory connection timeouts on 32-bit iPhones #40114

Closed

Description

@gspencergoog

I reverted two engine rolls in #40112 because the were causing failures in devicelab tests that were failing with timeouts trying to connect to the observatory: flutter_gallery_ios32__transition_perf and flutter_gallery_ios32__start_up.

I HAVE STOPPED THE ENGINE ROLL, so someone needs to restart it once this is resolved.

Specifically, they started failing when af07bb5 was committed, which includes a Dart roll that is probably suspect:

2019-09-06 [email protected] Roll src/third_party/dart be66176534..ec7ec4ecf7 (37 commits)

Here is a sample log output of one of the tests (both are similar):

2019-09-09T14:09:01.547976: stdout: [  +40 ms] (lldb)     run
2019-09-09T14:09:03.005319: stdout: [+1457 ms] success
stdout: [        ] (lldb)     safequit
2019-09-09T14:09:03.132474: stdout: [ +125 ms] Process 248 detached
2019-09-09T14:09:03.159828: stdout: [  +28 ms] Application launched on the device. Waiting for observatory port.
2019-09-09T14:21:27.297237: Task timed out in framework.dart after 0:15:00.000000.
Cleaning up after task...
2019-09-09T14:21:28.310369: Force-quitting process:
command : bin/flutter run --verbose --profile --trace-startup -d [device id redacted]
  started : 2019-09-09 14:06:29.482349
  pid     : 12227
2019-09-09T14:21:28.318085: "bin/flutter" exit code: -15
2019-09-09T14:21:29.329736: Task execution finished

Task failed with the following reason:
Timeout waiting for task process to exit: Future not completed

Activity

  1. gspencergoog commented on Sep 9, 2019

    @gspencergoog
    ContributorAuthor

    Note that reverting this also fixed a problem in flutter_gallery__back_button_memory. It's unclear if this engine roll is the culprit there, since it seemed to pass on the initial commit (but failed every build thereafter until I reverted this). And it's also not on 32-bit iOS, so there may be concurrent unconnected problems here.

  2. blasten commented on Sep 10, 2019

    @blasten

    Should we still keep the TODAY label @gspencergoog ?

  3. tvolkert commented on Sep 10, 2019

    @tvolkert
    Contributor

    Yes, this should stay TODAY, as the engine auto-roller is blocked on reverting the culprit in the engine or Dart SDK.

  4. assigned and unassigned on Sep 10, 2019
  5. mklim commented on Sep 10, 2019

    @mklim
  6. mklim commented on Sep 11, 2019

    @mklim
  7. added 3 commits that reference this issue on Sep 11, 2019
  8. mklim commented on Sep 11, 2019

    @mklim
    Contributor

    Okay, I can reliably reproduce this now. It has to do with profile mode specifically. Just flutter run or building the engine in debug mode isn't enough to repro. But flutter run --profile will briefly launch the app, the app will crash, and then the tool will hang.

    The log I mentioned above doesn't appear with this. I think it was just a one-off local build error.

  9. 14 remaining items

  10. aam commented on Sep 12, 2019

    @aam
    Member

    Sent out https://dart-review.googlesource.com/c/sdk/+/116883 with revert in dart sdk, so dart-to-engine roll can be resumed

  11. sjindel-google commented on Sep 12, 2019

    @sjindel-google
    Contributor

    @mklim What app did you run to reproduce the crash? Also, did it happen on 64-bit iOS or only 32-bit?

  12. aam commented on Sep 12, 2019

    @aam
    Member

    @sjindel-google I used flutter gallery (in profile/release mode). ios 32-bit was the only affected as far as I know.

  13. mklim commented on Sep 12, 2019

    @mklim
    Contributor

    @sjindel-google my testing was the same as @aam's.

  14. mklim commented on Sep 12, 2019

    @mklim
    Contributor

    I've resumed the dart to engine roller since the revert landed in dart-lang/sdk@0c481a1. I think it's safe to consider this fixed now.

  15. added a commit that references this issue on Sep 12, 2019
  16. added a commit that references this issue on Sep 30, 2019
  17. github-actions commented on Aug 28, 2021

    @github-actions

    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 -v and a minimal reproduction of the issue.

  18. locked as resolved and limited conversation to collaborators on Aug 28, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

dependency: dartDart team may need to help use: device-specificOnly manifests on certain devicesengineflutter/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