Skip to content
This repository was archived by the owner on Feb 25, 2025. It is now read-only.

Conversation

@chinmaygarde
Copy link
Contributor

There is a possibility for a VM launch to not have a requisite shutdown if a previous launch asked to leak the VM instance in the process. Embedders have to ensure (via their Embedding APIs) that all instances of VM launch use consistent settings.

@chinmaygarde chinmaygarde merged commit 876c4c3 into flutter:master Apr 18, 2019
@chinmaygarde chinmaygarde deleted the leak_assert branch April 18, 2019 00:25
engine-flutter-autoroll added a commit to engine-flutter-autoroll/flutter that referenced this pull request Apr 18, 2019
…ion on whether the VM should be leaked in the process. (flutter/engine#8622)
engine-flutter-autoroll added a commit to flutter/flutter that referenced this pull request Apr 18, 2019
flutter/engine@7679474...876c4c3

git log 7679474..876c4c3 --no-merges --oneline
876c4c3 Assert that all VM launches in the process have the same opinion on whether the VM should be leaked in the process. (flutter/engine#8622)
72c84c2 Revert "Roll src/third_party/dart 7b9ab9f353..714a082a5d (7 commits)" (flutter/engine#8624)
f017fe7 Avoid manually shutting down engine managed isolates. (flutter/engine#8621)
80e934e Roll src/third_party/dart 7b9ab9f353..714a082a5d (7 commits)

The AutoRoll server is located here: https://autoroll.skia.org/r/flutter-engine-flutter-autoroll

Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+/master/autoroll/README.md

If the roll is causing failures, please contact the current sheriff (cbracken@google.com), and stop
the roller if necessary.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants