Chrome unnecessarily attempts to clear legacy Icing corpus on every cold start |
|||
Issue descriptionChrome Version: M60 OS: Android What steps will reproduce the problem? (1) Run adb logcat to stream logs (2) Cold start Clank What is the expected result? It should clear the legacy Icing corpus only once, and cold start later shouldn't do it again. What happens instead? This message is printed in adb log: D/cr_Icing(25628): [ChromeGoogleApiClientImpl.java:68] Connection to GmsCore successful. E/cr_Icing(25628): Failed to clear legacy corpus. Status Code: 8 Message: No CorpusConfig for history of com.chrome.beta
,
Jul 11 2017
The following revision refers to this bug: https://chrome-internal.googlesource.com/clank/internal/apps/+/1f84ad0e8dc73ba0cf9f820e41f491e86eb1cceb commit 1f84ad0e8dc73ba0cf9f820e41f491e86eb1cceb Author: Wei-Yin Chen (陳威尹) <wychen@chromium.org> Date: Tue Jul 11 02:52:08 2017
,
Jul 11 2017
,
Jul 18 2017
Verified on Canary 61.0.3155.0 |
|||
►
Sign in to add a comment |
|||
Comment 1 by wychen@chromium.org
, Jul 6 2017