Repository navigation
Windows_android native_assets_android is 2.00% flaky #146236
Description
Activity
[2024-03-29 12:48:42.813650] [STDOUT] stderr: [ ] Caused by: java.lang.OutOfMemoryError: Java heap space [2024-03-29 12:48:42.813650] [STDOUT] stderr: [ ] at java.base/java.io.ByteArrayOutputStream.<init>(ByteArrayOutputStream.java:81) [2024-03-29 12:48:42.813650] [STDOUT] stderr: [ ] at com.android.zipflinger.NoCopyByteArrayOutputStream.<init>(NoCopyByteArrayOutputStream.java:27)That doesn't sound good for a small testing app.
<ffi_package_name>/example/android/gradle.properties:
org.gradle.jvmargs=-Xmx4G android.useAndroidX=true android.enableJetifier=trueI believe this should give the JVM 4 GB of memory.
In the logs I see 11 times
-Xmx4Gand one time-Xmx512mthe latter one the last mention of-Xmxbefore theOutOfMemoryError.Similar issue:
@stuartmorgan @reidbaker It is suspect that
Gradle Worker Daemon 1has a different heap limit. I have no clue where this worker is coming from though. Any insights?@dcharkes try
org.gradle.jvmargs=-Xmx4G -XX:MaxMetaspaceSize=2G -XX:+HeapDumpOnOutOfMemoryErrorIt is the default app template that is used for the plugin_ffi example:
org.gradle.jvmargs=-Xmx4G -XX:+HeapDumpOnOutOfMemoryError android.useAndroidX=true android.enableJetifier=trueI can make a PR to change that one.
- added a commit that references this issue
on Apr 4, 2024 Does the bot automatically mark the test as unflaky? I don't think I updated that status file.
Edit: This one: https://github.com/flutter/flutter/pull/146237/files
This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of
flutter doctor -vand a minimal reproduction of the issue.- locked as resolved and limited conversation to collaborators
on Apr 18, 2024
The post-submit test builder
Windows_android native_assets_androidhad a flaky ratio 2.00% for the past (up to) 100 commits, which is above our 2.00% threshold.One recent flaky example for a same commit: https://ci.chromium.org/ui/p/flutter/builders/prod/Windows_android%20native_assets_android/990
Commit: bca1d6a
Flaky builds:
https://ci.chromium.org/ui/p/flutter/builders/prod/Windows_android%20native_assets_android/990
https://ci.chromium.org/ui/p/flutter/builders/prod/Windows_android%20native_assets_android/981
Recent test runs:
https://flutter-dashboard.appspot.com/#/build?taskFilter=Windows_android%20native_assets_android
Please follow https://github.com/flutter/flutter/wiki/Reducing-Test-Flakiness#fixing-flaky-tests to fix the flakiness and enable the test back after validating the fix (internal dashboard to validate: go/flutter_test_flakiness).