Issue metadata
Sign in to add a comment
|
chrome.exe --diagnostics fails but probably shouldn't |
||||||||||||||||||
Issue description
Chrome Version: 62.0.3202.94
OS: Windows NT 10.0.14393
What steps will reproduce the problem?
(1) run chrome.exe --diagnostics
(2)
(3)
What is the expected result?
pass, I suppose?
What happens instead?
[FAIL] User data path
Path contents too large (2730528917) for: C:\Users\wfh\AppData\Local\Google\Chrome\User Data
[FAIL] App dictionaries directory path
Path provider failure
Please use labels and text to provide additional information.
These should probably pass. Also, should we remove this... Or maybe just expand it to make it more useful? I can think of a number of situations where we might want to have customers run this and provide us with info.
For graphics-related bugs, please copy/paste the contents of the about:gpu
page at the end of this report.
,
Nov 21 2017
perform diagnostics :) I think it's a very old part of code that cpu@ added a long while back. it's possible we might want to remove or improve this, I can see a number of things that might be useful e.g. for starters: trying to start sandboxed process and doing additional diagnostics if it fails.
,
Nov 21 2017
"TODO(cpu): There are a few maximum file sizes hard-coded in this file that have little or no theoretical or experimental ground. Find a way to justify them." It looks like our userdata limit is 850mb; mine's also about 2.5gb. https://cs.chromium.org/chromium/src/chrome/browser/diagnostics/recon_diagnostics.cc?sq=package:chromium&l=218 I really like the idea in #2 regarding sandboxed subprocesses.
,
Nov 21 2017
The two that fail in #0 pass for me, but I fail "User preferences integrity" and "Local state integrity" with "File too big" fwiw.
,
Jan 10
Downgrading P2s that haven't been modified in more than 6 months, which have no component or owner. |
|||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||
Comment 1 by brucedaw...@chromium.org
, Nov 21 2017