Issue metadata
Sign in to add a comment
|
${user_name} variable causes crash when used in UserDataDir path.
Reported by
ianedwa...@varndean.co.uk,
Mar 15 2017
|
||||||||||||||||||||
Issue description
UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/56.0.2924.87 Safari/537.36
Steps to reproduce the problem:
1. Start Chrome
2. Crash
What is the expected behavior?
Chrome Starts and the users data is stored in a custom area on the local C drive (C:\ChromeData\${user_name}) as per the Group Policy setting.
This worked in previous versions.
What went wrong?
Chrome Crashes on Startup. No logs created only an exception error is displayed: 0xc0000005
Crashed report ID: No
How much crashed? Whole browser
Is it a problem with a plugin? No
Did this work before? Yes 56.0.2924.87
Chrome version: 57.0.2987.98 Channel: stable
OS Version: 7
Flash Version: Shockwave Flash 25.0 r0
To get Chrome to start without crashing I removed the ${user_name} variable from UserDataDir registry value:
"C:\ChromeData\${user_name}"
to
"C:\ChromeData"
,
Mar 16 2017
This issue seems similar to the bug 700371 .Hence merging this into 700371. Please feel free to undupe if not similar. Thanks, |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by woxxom@gmail.com
, Mar 15 2017