Determine if prerendering on svelte devices while chrome is active causes crashes |
|||
Issue descriptionInitial descriptions of prerendering were that it sometimes fails on android devices with less than 512MB of memory. However, in our testing we have not seen that happen. Before enabling the feature more broadly, we should run an experiment to determine if enabling this feature affects the crash rate noticeably.
,
Jan 26 2017
Running a finch experiment after local tests indicate no problems.
,
Jan 30 2017
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/3532d6ed361f9633973673c9c49ca7bbc8f1e4e4 commit 3532d6ed361f9633973673c9c49ca7bbc8f1e4e4 Author: petewil <petewil@chromium.org> Date: Mon Jan 30 20:19:24 2017 Add finch configuration for the OfflinePagesSvelte finch test. BUG= 682525 Review-Url: https://codereview.chromium.org/2657883002 Cr-Commit-Position: refs/heads/master@{#447049} [modify] https://crrev.com/3532d6ed361f9633973673c9c49ca7bbc8f1e4e4/testing/variations/fieldtrial_testing_config.json
,
Feb 27 2018
Fix crbug.com/686925 before investigating this.
,
Aug 24
Let's give up on this. We found out that we promised android to only have one or two renderers open in Clank, and it would take a big change to chrome to make that promise for background rendering. |
|||
►
Sign in to add a comment |
|||
Comment 1 by dim...@chromium.org
, Jan 25 2017