Issue metadata
Sign in to add a comment
|
Heap profiling appears to crash Chrome on ChromeOS, preventing log-in |
||||||||||||||||||||||
Issue descriptionChrome Version: 60.0.3112.41 OS: ChromeOS (Caroline) What steps will reproduce the problem? (1) Sign-in to ChromeOS. (2) Open about:flags and set "heap profiling" to "pseudo" or "native". (3) Restart & sign-in again. What is the expected result? Expect that ChromeOS runs, with heap-profiling enabled. What happens instead? When signing back in at #3, the device goes blank for a few seconds, then returns to the sign-in screen. User has to remove the account from the device, and then re-add it, in order to be able to log-in to the device successfully. There is no tell-tale logging in the Chrome logs; I'll repro again and check the system logs for clues.
,
Jun 26 2017
For my own education, what is the process model on CrOS? Specifically: - are there any other non-chrome processes that use base? - If yes, do they get the same commandline from chrome? #1 is a plausible theory if there are lot of processes that end up using base, but needs verification. |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by dskiba@chromium.org
, Jun 26 2017