Chromium does not function after AppData\Local\Chromium becomes a symlink
Reported by
pasthe...@gmail.com,
Nov 16 2017
|
||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:57.0) Gecko/20100101 Firefox/57.0 Steps to reproduce the problem: 1. Install Chromium, use it for a while, install extensions. 2. While Chromium not running move the directory somewhere and make a dir symlink with mklink.exe instead of its dir. 3. Launch Chromium see also: https://bugs.chromium.org/p/chromium/issues/detail?id=750597 What is the expected behavior? What went wrong? After stating Chromium previously opened tabs on the tab bar appear, but the viewport in the tabs themselves are completely blank with a solid dark grey/black color. Popups in the lower right corner pile up notifying about crashed extensions. (FlashBlock, ChromeIFox, etc.) Did this work before? N/A Chrome version: 64.0.3269.0 Channel: dev OS Version: 10.0 Flash Version: Shockwave Flash 27.0 r0
,
Nov 29
Issue has not been modified or commented on in the last 365 days, please re-open or file a new bug if this is still an issue. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot |
||
►
Sign in to add a comment |
||
Comment 1 by rbasuvula@chromium.org
, Nov 29 2017Components: Platform>Extensions
Labels: Needs-Triage-M64 TE-NeedsTriageHelp