Chromium cannot start after AppData\Local\Chromium becomes a symlink
Reported by
pasthe...@gmail.com,
Jul 31 2017
|
||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/62.0.3169.0 Safari/537.36 Steps to reproduce the problem: 1. Install Chromium, install extensions, use it for some time, find it takes up more than 1GB of space 2. While Chromium not running relocate it to a different volume/drive, and put a NTFS directory symlink to C:\Users\<username>\AppData\Local\Chromium that points to the moved files/directories. 3. What is the expected behavior? Chromium functions, unaware of the change in persistence backing store subsystem. 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 purple-ish color. (GPU error in debug log.) Chromium reports a lot of extensions crashing. Did this work before? N/A Chrome version: 62.0.3169.0 Channel: n/a OS Version: 10.0 Flash Version:
,
Aug 3 2017
@pasthelod -- Thanks for reporting the issue. Could you please provide the details of the extensions used or sample extensions to reproduce the issue and consistent steps to reproduce the issue. This would help us in further investigating the issue. Thanks in advance.
,
Aug 3 2017
,
Oct 11 2017
Since reporter doesn't responded to comment #2, Closing this issue for now. pasthelod@ Could you please file a new bug if issue still exists in latest chrome builds.
,
Nov 16 2017
Sorry for taking this long. I can confirm, this still causes problems with Chromium 64.0.3269.0 (Developer Build) (32-bit). I'll open a new issue. |
||||
►
Sign in to add a comment |
||||
Comment 1 by ranjitkan@chromium.org
, Aug 2 2017