Issue metadata
Sign in to add a comment
|
Experiments are not listed in the Crash tool |
||||||||||||||||||||||
Issue descriptionChrome Version: Various; appears to affect at least as far back as M63. OS: ChromeOS (not sure if it affects other platforms). All the crash reports (across versions from M63 to M65) that I open show output under Fields->Experiments of the form: Count 52 IDs 0 6a89113b-ccb9a6a5f4a17dfedbc38-cf4f6ead4a17df6c6887-f7b8f67e47f4f43b2dc5-9370259047f4f4562a9-78c337f0b72d7ce-612a79a3ff277-e1cc0f1475-3d47f4f4 AppBannerTriggering: Unknown Group Alexei points out that this looks like the separators between the variation hashes are missing, preventing them from being correctly matched and reported.
,
Jan 3 2018
Hmmm, it seems this isn't common to all reports, after all. e.g. reports 28c57030bb9fdc07 and 25f80b4a80c88097 look fine, but reports 2f0d68100c2259ec, 675c5b877b13a29e and a172b2c2e6ba87fc are broken.
,
Jan 3 2018
Looking at the "Product Data" section, you can see that the variations-N chunks are where the corruption starts, which likely means this is an issue with the client-side data rather than the server-side processing. In Chrome 65, the crash key system has been completely replaced, so I'd be curious to see if the issue continues there.
,
Sep 20
wez: Is this still an issue?
,
Sep 20
Looking at some sample crashes from M68 they all look fine, so closing WontFix / obsolete for now. |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by rsesek@chromium.org
, Jan 3 2018