-
Notifications
You must be signed in to change notification settings - Fork 29.7k
Labels
P0Critical issues such as a build break or regressionCritical issues such as a build break or regressiona: imagesLoading, displaying, rendering imagesLoading, displaying, rendering imagesc: performanceRelates to speed or footprint issues (see "perf:" labels)Relates to speed or footprint issues (see "perf:" labels)customer: money (g3)engineflutter/engine related. See also e: labels.flutter/engine related. See also e: labels.frameworkflutter/packages/flutter repository. See also f: labels.flutter/packages/flutter repository. See also f: labels.perf: memoryPerformance issues related to memoryPerformance issues related to memorywaiting for PR to land (fixed)A fix is in flightA fix is in flight
Milestone
Description
Internal: b/157467549
If the app was put to background and then resumed, the GPU memory went back down.
not sure what the right approach for this. Changing the widget tree and not seeing an expected memory behavior is hard to explain. Is this a bug? Is it something that should be in documentation?
Metadata
Metadata
Assignees
Labels
P0Critical issues such as a build break or regressionCritical issues such as a build break or regressiona: imagesLoading, displaying, rendering imagesLoading, displaying, rendering imagesc: performanceRelates to speed or footprint issues (see "perf:" labels)Relates to speed or footprint issues (see "perf:" labels)customer: money (g3)engineflutter/engine related. See also e: labels.flutter/engine related. See also e: labels.frameworkflutter/packages/flutter repository. See also f: labels.flutter/packages/flutter repository. See also f: labels.perf: memoryPerformance issues related to memoryPerformance issues related to memorywaiting for PR to land (fixed)A fix is in flightA fix is in flight