New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 707553 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner: ----
Closed: Apr 2017
Cc:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug-Regression



Sign in to add a comment

"-user-data-dir" flag not working in latest Win10 stable? 57.0.2987.133

Reported by threecle...@gmail.com, Apr 2 2017

Issue description

UserAgent: Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/57.0.2987.133 Safari/537.36

Steps to reproduce the problem:
1. Sstart Chrome using a different data directory by running the following, either from a modified shortcut or the Run menu or from a command prompt: "C:\Program Files (x86)\Google\Chrome\Application\chrome.exe" -user-data-dir="C:\Users\(my user)\Documents\chrome profiles\(custom profile data directory)"

What is the expected behavior?
A Chrome instance launches using the custom data directory, with its own history, bookmarks, cache, etc, from the default instance.

What went wrong?
The default instance runs instead.

Did this work before? Yes Stable desktop version previous to 57.0.2987.133 I think? First noticed it early today, believe it was working normally yesterday

Chrome version: 57.0.2987.133  Channel: stable
OS Version: 10.0
Flash Version: 

This is the way I've run Chrome for years, using a folder of custom profile directories and a matching number of modified shortcuts - I love it because it allows me to easily run multiple instances of Chrome simultaneously, each signed into different accounts, with different extensions, history, bookmarks, etc.
 
Labels: Needs-Triage-M57
Thanks to a helpful reddit user I discovered that the flag works if I just change "-user-data-dir" to "--user-data-dir" (two dashes instead of one). This appears to be a change that happened with 57.0.2987.133 because I've been using my custom shortcuts (with the single dash) for literally years with no problems and they ALL stopped working at the same time a few days ago, around the time 57.0.2987.133 came out.

Anyway, updating them now. This was a PIA, wish we could get more of a heads up about stuff like this - there doesn't appear to be ANY mention of it in the release notes.
Cc: ranjitkan@chromium.org
Labels: -Needs-Triage-M57
Status: WontFix (was: Unconfirmed)
Thanks for the update, closing the issue as per above comments.

Sign in to add a comment