Assigned
Status Update
No update yet.
Comments
ch...@appspot.gserviceaccount.com
Execution failed for task ':app:compileMockDebugKotlin' means the Kotlin compiler failed: do you still have this issue? Do you see the actual error message (from the kotlin compiler) in the output?
ch...@appspot.gserviceaccount.com
🥪 Regression verification projects/62121018386/locations/us-central1/workflows/sandwich-verification-workflow-prod/executions/96986180-0bd5-4d6a-b7d6-07aba0ee87b3 job 11a8d46fa10000 for test: ChromiumPerf/android-pixel4-perf/system_health.memory_mobile/memory:chrome:all_processes:reported_by_chrome:cc:effective_size_avg/load_search/load_search_amazon_2019
reproduced the regression with statistic: {'control_median': 24135528, 'lower': 9.132502528060037, 'p_value': 1.2616270124166107e-06, 'treatment_median': 26503016, 'upper': 10.955821392907893}.
Proceed to bisection.
reproduced the regression with statistic: {'control_median': 24135528, 'lower': 9.132502528060037, 'p_value': 1.2616270124166107e-06, 'treatment_median': 26503016, 'upper': 10.955821392907893}.
Proceed to bisection.
ch...@appspot.gserviceaccount.com
📍 Pinpoint job created and queued.
https://pinpoint-dot-chromeperf.appspot.com/job/16e802e2610000
Created by chromeperf@appspot.gserviceaccount.com
Benchmark: system_health.memory_mobile
Story: load:search:amazon:2019
Measurement: memory:chrome:all_processes:reported_by_chrome:cc:effective_size
The job has been scheduled on the "android-pixel4-perf" queue which currently has
1 pending jobs.
Created by chromeperf@appspot.gserviceaccount.com
Benchmark: system_health.memory_mobile
Story: load:search:amazon:2019
Measurement: memory:chrome:all_processes:reported_by_chrome:cc:effective_size
The job has been scheduled on the "android-pixel4-perf" queue which currently has
1 pending jobs.
ch...@appspot.gserviceaccount.com
Automatic bisection started for measurement:
ChromiumPerf/android-pixel4-perf/system_health.memory_mobile/memory:chrome:all_processes:reported_by_chrome:cc:effective_size_avg/load_search/load_search_amazon_2019
To opt-out of further automatically started bisections for this issue, please
add the <b>Chromeperf-Auto-BisectOptOut</b> label.
ChromiumPerf/android-pixel4-perf/system_health.memory_mobile/memory:chrome:all_processes:reported_by_chrome:cc:effective_size_avg/load_search/load_search_amazon_2019
To opt-out of further automatically started bisections for this issue, please
add the <b>Chromeperf-Auto-BisectOptOut</b> label.
ch...@appspot.gserviceaccount.com
<b>📍 🥪 1 regressions found.</b>
https://pinpoint-dot-chromeperf.appspot.com/job/16e802e2610000
<b>Started sandwich culprit verification process.</b>
culprit verification workflow keys: ['projects/62121018386/locations/us-central1/workflows/sandwich-verification-workflow-prod/executions/68fcf9fe-a98a-4f64-84ee-e8527a253740']
<b>Started sandwich culprit verification process.</b>
culprit verification workflow keys: ['projects/62121018386/locations/us-central1/workflows/sandwich-verification-workflow-prod/executions/68fcf9fe-a98a-4f64-84ee-e8527a253740']
ch...@appspot.gserviceaccount.com
<b>📍 Found a significant difference at 1 commit.</b>
https://pinpoint-dot-chromeperf.appspot.com/job/16e802e2610000
<b>Set LimitLayerMergeDistance:limit/16 by default</b> by wangxianzhu@chromium.org
https://chromium.googlesource.com/chromium/src/+/728717eff66457327d5f632fce8c05fdc7fdd66d
memory:chrome:all_processes:reported_by_chrome:cc:effective_size: 2.42e+07 → 2.66e+07 (+2.395e+06) (+9.897%)
Understanding performance regressions:
http://g.co/ChromePerformanceRegressions
Benchmark documentation link:
https://bit.ly/system-health-benchmarks
You can view the full results and re-run the Pinpoint job at:
https://pinpoint-dot-chromeperf.appspot.com/job/16e802e2610000
If you think Pinpoint blamed the wrong commit, please add issue to
`Chromeperf-CulpritDetection-NeedsAttention` (hotlist:5670048) and
unassign yourself so that a sheriff can help diagnose.
<b>Set LimitLayerMergeDistance:limit/16 by default</b> by wangxianzhu@chromium.org
memory:chrome:all_processes:reported_by_chrome:cc:effective_size: 2.42e+07 → 2.66e+07 (+2.395e+06) (+9.897%)
Understanding performance regressions:
Benchmark documentation link:
You can view the full results and re-run the Pinpoint job at:
If you think Pinpoint blamed the wrong commit, please add issue to
`Chromeperf-CulpritDetection-NeedsAttention` (hotlist:5670048) and
unassign yourself so that a sheriff can help diagnose.
ch...@appspot.gserviceaccount.com
Reopened due to new regressions detected for this alert group:
Added 1 regressions to the group
Internal (Googlers-only) Reports:
- Chromium:https://chrome-perf.corp.goog/u/?anomalyGroupID=a16ae83b-416e-4c7e-a2ff-88ac0fa81fae
(Legacy)https://chromeperf.appspot.com/group_report?group_id=a16ae83b-416e-4c7e-a2ff-88ac0fa81fae
Top 1 affected measurements in android-pixel-tangor-perf:
- system_health.memory_mobile/memory:chrome:all_processes:reported_by_chrome:cc:effective_size_avg/load_search/load_search_amazon_2019
10.74%: 34958049.0 -> 38712940.0 sizeInBytes
Added 1 regressions to the group
Internal (Googlers-only) Reports:
- Chromium:
(Legacy)
Top 1 affected measurements in android-pixel-tangor-perf:
- system_health.memory_mobile/memory:chrome:all_processes:reported_by_chrome:cc:effective_size_avg/load_search/load_search_amazon_2019
10.74%: 34958049.0 -> 38712940.0 sizeInBytes
ch...@appspot.gserviceaccount.com
Alert group updated:
Added 1 regressions to the group
Internal (Googlers-only) Reports:
- Chromium:https://chrome-perf.corp.goog/u/?anomalyGroupID=a16ae83b-416e-4c7e-a2ff-88ac0fa81fae
(Legacy)https://chromeperf.appspot.com/group_report?group_id=a16ae83b-416e-4c7e-a2ff-88ac0fa81fae
Top 1 affected measurements in android-pixel6-pro-perf:
- system_health.memory_mobile/memory:chrome:all_processes:reported_by_chrome:cc:effective_size_avg/load_search/load_search_amazon_2019
11.62%: 37304440.0 -> 41638008.0 sizeInBytes
Added 1 regressions to the group
Internal (Googlers-only) Reports:
- Chromium:
(Legacy)
Top 1 affected measurements in android-pixel6-pro-perf:
- system_health.memory_mobile/memory:chrome:all_processes:reported_by_chrome:cc:effective_size_avg/load_search/load_search_amazon_2019
11.62%: 37304440.0 -> 41638008.0 sizeInBytes
ch...@appspot.gserviceaccount.com
Automatic regression verification started for measurement:
ChromiumPerf/android-pixel6-pro-perf/system_health.memory_mobile/memory:chrome:all_processes:reported_by_chrome:cc:effective_size_avg/load_search/load_search_amazon_2019
Verification workflow id: projects/62121018386/locations/us-central1/workflows/sandwich-verification-workflow-prod/executions/3ce3a420-8a76-44ac-b622-ca8093a2d82b
ChromiumPerf/android-pixel6-pro-perf/system_health.memory_mobile/memory:chrome:all_processes:reported_by_chrome:cc:effective_size_avg/load_search/load_search_amazon_2019
Verification workflow id: projects/62121018386/locations/us-central1/workflows/sandwich-verification-workflow-prod/executions/3ce3a420-8a76-44ac-b622-ca8093a2d82b
ch...@appspot.gserviceaccount.com
🥪 Regression verification projects/62121018386/locations/us-central1/workflows/sandwich-verification-workflow-prod/executions/3ce3a420-8a76-44ac-b622-ca8093a2d82b job 15420502610000 for test: ChromiumPerf/android-pixel6-pro-perf/system_health.memory_mobile/memory:chrome:all_processes:reported_by_chrome:cc:effective_size_avg/load_search/load_search_amazon_2019
reproduced the regression with statistic: {'control_median': 36846288, 'lower': 9.727966027436707, 'p_value': 7.3143536227782135e-06, 'treatment_median': 41179856, 'upper': 11.7622966954547}.
Proceed to bisection.
reproduced the regression with statistic: {'control_median': 36846288, 'lower': 9.727966027436707, 'p_value': 7.3143536227782135e-06, 'treatment_median': 41179856, 'upper': 11.7622966954547}.
Proceed to bisection.
ch...@appspot.gserviceaccount.com
📍 Pinpoint job created and queued.
https://pinpoint-dot-chromeperf.appspot.com/job/10320502610000
Created by chromeperf@appspot.gserviceaccount.com
Benchmark: system_health.memory_mobile
Story: load:search:amazon:2019
Measurement: memory:chrome:all_processes:reported_by_chrome:cc:effective_size
The job has been scheduled on the "android-pixel6-pro-perf" queue which currently has
1 pending jobs.
Created by chromeperf@appspot.gserviceaccount.com
Benchmark: system_health.memory_mobile
Story: load:search:amazon:2019
Measurement: memory:chrome:all_processes:reported_by_chrome:cc:effective_size
The job has been scheduled on the "android-pixel6-pro-perf" queue which currently has
1 pending jobs.
ch...@appspot.gserviceaccount.com
Automatic bisection started for measurement:
ChromiumPerf/android-pixel6-pro-perf/system_health.memory_mobile/memory:chrome:all_processes:reported_by_chrome:cc:effective_size_avg/load_search/load_search_amazon_2019
To opt-out of further automatically started bisections for this issue, please
add the <b>Chromeperf-Auto-BisectOptOut</b> label.
ChromiumPerf/android-pixel6-pro-perf/system_health.memory_mobile/memory:chrome:all_processes:reported_by_chrome:cc:effective_size_avg/load_search/load_search_amazon_2019
To opt-out of further automatically started bisections for this issue, please
add the <b>Chromeperf-Auto-BisectOptOut</b> label.
ch...@appspot.gserviceaccount.com
<b>📍 🥪 1 regressions found.</b>
https://pinpoint-dot-chromeperf.appspot.com/job/10320502610000
<b>Started sandwich culprit verification process.</b>
culprit verification workflow keys: ['projects/62121018386/locations/us-central1/workflows/sandwich-verification-workflow-prod/executions/08b6de2e-3dc4-4d68-a94c-ad6b0d5d2100']
<b>Started sandwich culprit verification process.</b>
culprit verification workflow keys: ['projects/62121018386/locations/us-central1/workflows/sandwich-verification-workflow-prod/executions/08b6de2e-3dc4-4d68-a94c-ad6b0d5d2100']
ch...@appspot.gserviceaccount.com
<b>📍 Found a significant difference at 1 commit.</b>
https://pinpoint-dot-chromeperf.appspot.com/job/10320502610000
<b>Set LimitLayerMergeDistance:limit/16 by default</b> by wangxianzhu@chromium.org
https://chromium.googlesource.com/chromium/src/+/728717eff66457327d5f632fce8c05fdc7fdd66d
memory:chrome:all_processes:reported_by_chrome:cc:effective_size: 3.783e+07 → 4.133e+07 (+3.507e+06) (+9.272%)
Understanding performance regressions:
http://g.co/ChromePerformanceRegressions
Benchmark documentation link:
https://bit.ly/system-health-benchmarks
You can view the full results and re-run the Pinpoint job at:
https://pinpoint-dot-chromeperf.appspot.com/job/10320502610000
If you think Pinpoint blamed the wrong commit, please add issue to
`Chromeperf-CulpritDetection-NeedsAttention` (hotlist:5670048) and
unassign yourself so that a sheriff can help diagnose.
<b>Set LimitLayerMergeDistance:limit/16 by default</b> by wangxianzhu@chromium.org
memory:chrome:all_processes:reported_by_chrome:cc:effective_size: 3.783e+07 → 4.133e+07 (+3.507e+06) (+9.272%)
Understanding performance regressions:
Benchmark documentation link:
You can view the full results and re-run the Pinpoint job at:
If you think Pinpoint blamed the wrong commit, please add issue to
`Chromeperf-CulpritDetection-NeedsAttention` (hotlist:5670048) and
unassign yourself so that a sheriff can help diagnose.
ap...@google.com
Project: chromium/src
Branch: main
Author: Xianzhu Wang <
Link:
Revert "Set LimitLayerMergeDistance:limit/16 by default"
Expand for full commit details
Revert "Set LimitLayerMergeDistance:limit/16 by default"
This reverts commit 728717eff66457327d5f632fce8c05fdc7fdd66d.
Reason for revert: The performance impact is unclear. We'll keep
the original default until we know the impact and find the best
value.
Original change's description:
> Set LimitLayerMergeDistance:limit/16 by default
>
> The number is chosen kind of arbitrarily. It doesn't seem to affect
> speedometer3 [1] and motionmark [2], but improves performance in the
> bug case (before we optimize generation of PaintChunks). Hopefully it
> will prevent worst case of layerization performance while doesn't
> change layerization results very much.
>
> (These were tested with limit/8)
> [1] https://pinpoint-dot-chromeperf.appspot.com/job/1674832fa10000
> [2] https://pinpoint-dot-chromeperf.appspot.com/job/13c01c68610000
>
> Bug: 40929618
> Change-Id: I8b509006c0b73dcef003fcb71ca180c6617b7259
> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6287967
> Reviewed-by: Philip Rogers <pdr@chromium.org>
> Commit-Queue: Xianzhu Wang <wangxianzhu@chromium.org>
> Cr-Commit-Position: refs/heads/main@{#1425874}
Bug: 40929618, 399698215
Change-Id: Id53cf44fafe346a788ff2a0a0bdd671ed4831518
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6318722
Reviewed-by: Philip Rogers <pdr@chromium.org>
Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com>
Commit-Queue: Xianzhu Wang <wangxianzhu@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1427308}
Files:
- M
third_party/blink/common/features.cc - M
third_party/blink/renderer/core/paint/compositing/compositing_test.cc - M
third_party/blink/web_tests/compositing/overflow/universal-accelerated-overflow-scroll-expected.txt - M
third_party/blink/web_tests/external/wpt/css/css-images/object-fit-none-png-001c.html - M
third_party/blink/web_tests/external/wpt/css/css-images/object-fit-none-png-002c.html - M
third_party/blink/web_tests/external/wpt/css/css-images/object-fit-scale-down-png-001c.html - M
third_party/blink/web_tests/external/wpt/css/css-images/object-fit-scale-down-png-002c.html - M
third_party/blink/web_tests/fast/events/touch/compositor-touch-hit-rects-scroll-expected.txt - M
third_party/blink/web_tests/platform/linux/compositing/overflow/universal-accelerated-overflow-scroll-expected.txt - M
third_party/blink/web_tests/platform/linux/fast/forms/textarea/basic-textareas-expected.png - M
third_party/blink/web_tests/platform/mac/paint/invalidation/image/canvas-composite-repaint-by-all-imagesource-expected.txt - M
third_party/blink/web_tests/platform/win/compositing/overflow/universal-accelerated-overflow-scroll-expected.txt - M
third_party/blink/web_tests/platform/win10/compositing/overflow/universal-accelerated-overflow-scroll-expected.txt
Hash: eee22cd21ec03b98bff4d1ad8d9b142d2df036e1
Date: Mon Mar 03 12:17:25 2025
Description
Internal (Googlers-only) Reports:
- Chromium:
(Legacy) Chromeperf Report:
Top 1 regressions (out of 1, with 0 improvements) in this group:
- ChromiumPerf/android-pixel4-perf/system_health.memory_mobile/memory:chrome:all_processes:reported_by_chrome:cc:effective_size_avg/load_search/load_search_amazon_2019
11.71%: 24135528.0 -> 26961168.0 sizeInBytes
Top 1 affected measurements in android-pixel4-perf:
- system_health.memory_mobile/memory:chrome:all_processes:reported_by_chrome:cc:effective_size_avg/load_search/load_search_amazon_2019
11.71%: 24135528.0 -> 26961168.0 sizeInBytes
Regressions grouped by system_health.memory_mobile includes data from the following benchmarks with listed owners:
system_health.memory_mobile: lizeb@chromium.org, pasko@chromium.org
Commits in this range:
Chromium Git Hash:
Chromium Commit Position:
V8 Commit Position:
WebRTC Git Hash: