Prior to the 1.26 Release of a Flutter, multiple Flutter Engine instances were generated if multiple Flutter pages were started. Each Engine occupied a large amount of memory. Many apps are eager to solve this problem. This gives a Boost to the Flutter Engine, which provides a multi-page sharing Engine. However, when multiple Flutter pages need to be displayed at the same time (such as a split screen on iOS or a multi-page application on Huawei mobile phone), only one of the Flutter pages will be normal and the other one will be blank. On the Android side you can use multiple processes to solve this problem, but to completely solve the problem, or multiple Engine support, and each Engine can not take up too much memory. (Still losing hair today)
After seeing the 2.0 update, I couldn’t wait to see the update content, and sure enough, she came
The current memory footprint for each additional Flutter instance beyond the first instance is ~180kB on Android and iOS. On Android and iOS, with the exception of the first one, the current memory usage of every other Flutter instance is ~ 180kB
Dev.dev /docs/develo…
Dev /docs/develo…
This feature is not in stable release yet, but it will be soon. This update gives me more confidence in Flutter as a true cross-platform solution. If you are interested in Flutter, learning about Flutter is already an advantage. There are currently job postings for Flutter development engineers on websites.
Reference: medium.com/flutter/wha…