- 04 9月, 2020 7 次提交
-
-
由 gaaclarke 提交于
Started printing out error messages when the observatory won't be reachable because of permissions problems. (#20960)
-
由 LongCatIsLooong 提交于
-
由 skia-flutter-autoroll 提交于
-
由 skia-flutter-autoroll 提交于
-
由 skia-flutter-autoroll 提交于
-
由 Emmanuel Garcia 提交于
-
由 Nathan Rogers 提交于
This change reverts https://github.com/flutter/engine/pull/15900. The design of the expected consumer of the original PR changed, and the feature ended up going unused. Since the unexpected difference in trace event routing behavior has mostly ended up as a source of confusion, change things back to route trace events to Fuchsia system tracing on all configurations.
-
- 03 9月, 2020 18 次提交
-
-
由 skia-flutter-autoroll 提交于
-
由 skia-flutter-autoroll 提交于
-
由 skia-flutter-autoroll 提交于
-
由 skia-flutter-autoroll 提交于
-
由 skia-flutter-autoroll 提交于
-
由 Emmanuel Garcia 提交于
-
由 skia-flutter-autoroll 提交于
-
由 skia-flutter-autoroll 提交于
-
由 Emmanuel Garcia 提交于
-
由 nturgut 提交于
* renaming e2e tests to integration * change the name of the files in the blocked list
-
由 skia-flutter-autoroll 提交于
-
由 Dan Field 提交于
-
由 Dan Field 提交于
* Use hint freed specifically for image disposal
-
由 skia-flutter-autoroll 提交于
-
由 skia-flutter-autoroll 提交于
-
由 Alexander Aprelev 提交于
* Log exception in addition to the stack trace for unhandled exceptions. Having exception logged can be especially useful when stack trace is blank.
-
由 skia-flutter-autoroll 提交于
-
由 skia-flutter-autoroll 提交于
-
- 02 9月, 2020 15 次提交
-
-
由 Emmanuel Garcia 提交于
* Clear the GL context only after submitting the frame * Fix Screenshot test
-
由 Gary Qian 提交于
-
由 skia-flutter-autoroll 提交于
-
由 Jim Graham 提交于
This reverts commit 58a62076.
-
由 Gábor 提交于
* `Image.toByteData()` was not implemented in either DomCanvas or CanvasKit. This PR covers **both.** * `Picture.toImage()` was not implemented in either DomCanvas or CanvasKit. This PR covers **CanvasKit**
-
由 Emmanuel Garcia 提交于
-
由 skia-flutter-autoroll 提交于
-
由 Alexander Brusher 提交于
-
由 chenjianguang 提交于
## Description As the related issue refer, the application may be doing too much work on its main thread even in a simple hello_world demo. That is because the creation of `Engine` on the ui thread takes a noticeable time, and it is blocking the platform thread in order to run `Shell::Setup` synchronously. The cost of `Engine`'s constructor is mainly about the creating of root isolate. Actually, there used to be another time-consuming process, the default font manager setup, which was resolved by https://github.com/flutter/engine/pull/18225. Similar to https://github.com/flutter/engine/pull/18225, this pr move the creation of root isolate out from creating `Engine`. After this action, the main thread blocking is quite an acceptable slice. ## Related Issues https://github.com/flutter/flutter/issues/40563 could be resolved by this pr.
-
由 skia-flutter-autoroll 提交于
-
由 skia-flutter-autoroll 提交于
-
由 skia-flutter-autoroll 提交于
-
由 stuartmorgan 提交于
The C++ wrapper makes heavy use of templates to support arbitrary types in the platform channel classes, but in practice EncodableValue is what essentially all code will use. This defaults those template types to reduce boilerplate in plugin code (e.g., allowing the use of MethodChannel<> instead of MethodChannel<EncodableValue>).
-
由 skia-flutter-autoroll 提交于
https://dart.googlesource.com/sdk.git/+log/6eab35f49cbb..2a5f37d25453 2020-09-01 dart-luci-ci-builder@dart-ci.iam.gserviceaccount.com Version 2.10.0-80.0.dev If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/dart-sdk-flutter-engine Please CC dart-vm-team@google.com on the revert to ensure that a human is aware of the problem. To report a problem with the AutoRoller itself, please file a bug: https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+doc/master/autoroll/README.md
-