I have an experiment, if anyone is willing to perform it.

Apply this patch in flutter:

diff --git a/packages/flutter_tools/lib/src/compile.dart b/packages/flutter_tools/lib/src/compile.dart
index cdfa2fc37f..ba7491f091 100644
--- a/packages/flutter_tools/lib/src/compile.dart
+++ b/packages/flutter_tools/lib/src/compile.dart
@@ -107,6 +107,9 @@ class StdoutHandler {
     if (_badState) {
       return;
     }
+    if (message.startsWith('Observatory listening on')) {
+      return;
+    }
     const String kResultPrefix = 'result ';
     if (boundaryKey == null && message.startsWith(kResultPrefix)) {
       boundaryKey = message.substring(kResultPrefix.length);
@@ -706,6 +709,9 @@ class DefaultResidentCompiler implements ResidentCompiler {
     );
     final List<String> command = <String>[
       globals.artifacts.getArtifactPath(Artifact.engineDartBinary),
+      '--old_gen_heap_size=1000',
+      '--enable-vm-service=12345',
+      '--disable-service-auth-codes',
       frontendServer,
       '--sdk-root',
       sdkRoot,

Remove the files

bin/cache/flutter_tools.snapshot
bin/cache/flutter_tools.stamp

and try again (i.e. flutter run etc).

This does a few things:

It limits the amount of memory that the dart vm "frontend_sever" should be able to use so it hopefully won't crash any computers because of low ram
it enables observatory for the dart vm "frontend_sever" without the so called 'auth codes' (on port 12345)
By removing the files it forces a new snapshot to be created (meaning the changes will take effect).

There is some risk that this will simply just not be enought memory (given that you are experiencing huge memory consumptions) and that flutter run will fail saying something like

Exhausted heap space, trying to allocate 16464 bytes.           
../../third_party/dart/runtime/vm/object.cc: 2583: error: Out of memory.
[...]

-- in which case (and if you're computer doesn't crash by doing so) you could update the -old_gen_heap_size=1000 line to give it more memory.

Now assuming the process doesn't crash and you still get high memory usage, you can open up your browser to http://localhost:12345 --- the so called "dart observatory" where you can do a heap snapshot as discusseed in #40243 (comment).
The allocation profile could also be interesting (allocation profile and click Download at the top).

If anyone could share such things with me at jensj@google.com that would be great. (It might not be enough to actually get to the root of this (a reproduction would be better), but it certainly won't hurt).

Uh oh!

frontend_server process is consuming a lot of memory after Flutter 1.17 upgrade #41862

Description

Metadata

Metadata

Assignees

Labels

Type

Fields

Projects

Milestone

Relationships

Development

Issue actions