- 11 5月, 2020 1 次提交
-
-
由 Marcus Tomlinson 提交于
Added a new `FlutterEngineAOTData` argument to `FlutterProjectArgs`. Embedders can instantiate and destroy this object via the new `FlutterEngineCreateAOTData` and `FlutterEngineCollectAOTData` methods provided. If an embedder provides more than one source of AOT data to `FlutterEngineInitialize` or `FlutterEngineRun` (e.g. snapshots as well as `FlutterEngineAOTData`), the engine will error out. Resolves: https://github.com/flutter/flutter/issues/50778
-
- 10 5月, 2020 1 次提交
-
-
由 Jason Simmons 提交于
This was accidentally removed in https://github.com/flutter/engine/pull/18182
-
- 09 5月, 2020 1 次提交
-
-
由 Gary Qian 提交于
-
- 08 5月, 2020 8 次提交
-
-
由 xster 提交于
-
由 Robert Ancell 提交于
Classs for binary message encoding/decoding that matches the ones in the Flutter services library.
-
由 Robert Ancell 提交于
FlValue is a lightweight object used to contain the value types that Flutter uses on platform channels.
-
由 stuartmorgan 提交于
This does some long-overdue refactoring of the spaghetti code that grew in the GLFW embedding to begin providing a clearer separation between the engine and the window. It is now possible to register plugins, and run the runloop, on a headless engine, which makes headless mode much more usable. This is useful in some automated testing environments. There is more refactoring that should be done in the future, but this is a good incremental point to stop as the PR is already large, and it provides useful new functionality as-is.
-
由 Kurun 提交于
Fixes https://github.com/flutter/flutter/issues/49398
-
由 Robert Ancell 提交于
* Handle leak of message handle when no engine present * Move callback in wrong location
-
由 xster 提交于
-
由 Jason Simmons 提交于
The engine was using a global to store a timestamp representing the launch of the engine. This timestamp is initialized with a JNI call on Android and during shell setup on other platforms. Later the timestamp is added to a FlutterEngineMainEnter timeline event used to measure engine startup time in benchmarks. This PR removes the global and the JNI call and moves the timestamp into the settings object.
-
- 07 5月, 2020 3 次提交
-
-
由 Kaushik Iska 提交于
See flutter.dev/go/engine-cpu-profiling for details
-
由 Wu Zhong 提交于
-
由 Ali Mahdiyar 提交于
-
- 06 5月, 2020 2 次提交
-
-
由 Robert Ancell 提交于
-
由 Chris Yang 提交于
-
- 05 5月, 2020 2 次提交
-
-
由 Jason Simmons 提交于
-
由 Robert Ancell 提交于
-
- 04 5月, 2020 1 次提交
-
-
由 Robert Ancell 提交于
-
- 02 5月, 2020 4 次提交
-
-
由 gabeschine 提交于
This change is part of an LSC in Fuchsia, and is a functionality no-op. Fixes fxbug.dev/50759 Co-authored-by: NGabriel Schine <thatguy@google.com>
-
由 Chinmay Garde 提交于
The way transactions were added changed in https://github.com/flutter/engine/commit/68fd8334889610af08cbfc2828f91cf14faf3f1d. This broke rendering using both Metal and OpenGL when no implicit transaction was present on the transaction stack. The failure models differ based on Metal vs. OpenGL and iOS/device versions. On older versions of iOS, rendering would consume memory till exhaustion. On newer iOS versions, rendering would be stuck (till a timeout). This patch brings transaction management back in line with as it was earlier and also makes the Metal backend resilient to transactions being present on the transaction stack at all. Since this is still quite brittle, transaction management must be moved to IOSSurface as a followup. Fixes https://github.com/flutter/flutter/issues/55784.
-
由 Alexander Aprelev 提交于
* Revert "Do not register UI-related native functions in secondary isolates (#6401)" This reverts commit 69ae5694 as it doesn't work when root and secondary isolates run in the same isolate group. * Confirm it is root isolate that makes UI native calls. * Fix format, UIDartState reference from Fuchsia source * No UI isolate check for fuchsia calls * Fix typo. Remove redundant runtime calls
-
- 01 5月, 2020 6 次提交
-
-
由 Felipe Archondo 提交于
In order to better support different products on Fuchsia, we should change performance-sensitive attributes based on config files passed in. This change does so for `vsync_offset`.
-
由 stuartmorgan 提交于
When creating a console on Windows, stdout/stderr aren't wired up to it. They need to be re-opened afeter the console is created, and that needs to be done separately in the engine due to the use of static runtime linking. This provides a helper method that the runner can call when creating a console so that output will work as expected. Part of https://github.com/flutter/flutter/issues/53169
-
由 George Wright 提交于
Bundle the validation layers and enable them if --enable-vulkan-validation-layers is specified to gn (#17854)
-
由 Kaushik Iska 提交于
This is to reduce log spam. Fixes: https://github.com/flutter/flutter/issues/55966
-
由 Filip Filmar 提交于
This functionality is added in issue #41523. Allows runners to request the singleton instance of `sys::ComponentContext`, while it remains also accessible to component-specific code that does not have direct access to top-level objects. Fixes #41523
-
由 Wings006 提交于
-
- 30 4月, 2020 3 次提交
-
-
由 stuartmorgan 提交于
The existing logic incorrectly factored out a check that there were arguments too early, applying it to any message not already handled (including unhandled methods, such as methods added after the initial implementation) and thus failing if any unhandled message had no arguments. Fixes https://github.com/flutter/flutter/issues/55653
-
由 Chinmay Garde 提交于
Fixes https://github.com/flutter/flutter/issues/55783 Requires follow-up https://github.com/flutter/flutter/issues/55926
-
由 Robert Ancell 提交于
-
- 29 4月, 2020 4 次提交
-
-
由 Robert Ancell 提交于
-
由 George Wright 提交于
-
-
由 xster 提交于
-
- 28 4月, 2020 1 次提交
-
-
由 gaaclarke 提交于
-
- 27 4月, 2020 1 次提交
-
-
由 Emmanuel Garcia 提交于
-
- 25 4月, 2020 1 次提交
-
-
由 xster 提交于
-
- 24 4月, 2020 1 次提交
-
-
由 Robert Ancell 提交于
GTK uses timestamps in milliseconds, Flutter wants them in microseconds.
-