Duplicate of  issue 9862 

Unable to reproduce the issue on windows 7, Linux Ubuntu 14.04 and Mac 10.11.6 using chrome version 54.0.2840.99 with the below steps

1. Start chrome from command line Chrome://version or chrome://flags
2.chrome opened with URL chrome://chrome-signin/?access_point=0&reason=0

Please find the attached screen cast and confirm anything missed here.
Request you once please try the issue by upgrading chrome to latest stable and update the thread if the issue still persists.

Thanks,

The attached screencast shows the sign in tab which is most probably a default page if the user is not signed in. It should show the chrome://memory-internals in the recorded example.

Attached a screencast as a guest user, which shows the blank url.

Deleted: chrome-open-url.webm 1.6 MB

	chrome-open-url.webm 1.6 MB View Download

#2, #3, #4: the reason chrome:// urls aren't supported is explained by the  issue 9862 , which I've linked in #1.

As you can see in the source code:
https://cs.chromium.org/chromium/src/chrome/browser/ui/startup/startup_browser_creator.cc

	std::vector<GURL> StartupBrowserCreator::GetURLsFromCommandLine(

	    .............................

	    const GURL settings_url = GURL(chrome::kChromeUISettingsURL);
	    bool url_points_to_an_approved_settings_page = false;
	#if defined(OS_CHROMEOS)
	    // In ChromeOS, allow any settings page to be specified on the command line.
	    url_points_to_an_approved_settings_page =
	        url.GetOrigin() == settings_url.GetOrigin();
	#else
	    // Exposed for external cleaners to offer a settings reset to the
	    // user. The allowed URLs must match exactly.
	    const GURL reset_settings_url =
	        settings_url.Resolve(chrome::kResetProfileSettingsSubPage);
	    url_points_to_an_approved_settings_page = url == reset_settings_url;
	#if defined(OS_WIN)
	    // On Windows, also allow a hash for the Chrome Cleanup Tool.
	    const GURL reset_settings_url_with_cct_hash = reset_settings_url.Resolve(
	        std::string("#") +
	        settings::ResetSettingsHandler::kCctResetSettingsHash);
	    url_points_to_an_approved_settings_page =
	        url_points_to_an_approved_settings_page ||
	        url == reset_settings_url_with_cct_hash;
	#endif  // defined(OS_WIN)
	#endif  // defined(OS_CHROMEOS)

	    .............................

	    if (policy->IsWebSafeScheme(url.scheme()) ||
	        url.SchemeIs(url::kFileScheme) ||
	        url_points_to_an_approved_settings_page ||
	        (url.spec().compare(url::kAboutBlankURL) == 0)) {
	      urls.push_back(url);
	    }
	  }
	  return urls;
	}

It means the following:

* In ChromeOS, any chrome://settings page may be specified on the command line
* On other platforms only chrome://settings/resetProfileSettings is allowed.
* Web-safe schemes are allowed  http://, https://, ftp://, data:, feed, blob:
* real file paths like c:\something.html 
* about:blank.

In other words, all chrome:// urls are ignored on the command line with the exception mentioned above.

Thank you for providing more feedback. Adding requester "kavvaru@chromium.org" for another review and adding "Needs-Review" label for tracking.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Cleaning up "Needs-Review" label as we are not using this label for triage anymore. Ref bug for this cleanup 684919

Agreed with comment 5; this seems intentional.