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

Issue 599583 link

Starred by 2 users
Status: WontFix
Owner:
█ wnwen@chromium.org
OOO until Feb 4th
Closed: May 2016
Cc:
█ mlliu@chromium.org
█ hzl@chromium.org
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 3
Type: Bug



Sign in to add a comment

chrome://crashes UI doesn't acknowledge comand line flags.

Project Member Reported by hzl@chromium.org, Mar 31 2016 
Version: 51.0.2695.0
OS: Nexus 6

What steps will reproduce the problem?
(1) build/android/adb_chrome_public_command_line --force-dump-upload --enable-crash-reporter-for-testing
(2) ninja -C out/Debug -j3000 -l30 chrome_apk
(3) chrome://crashes still say crash reporting disabled.

What is the expected output?
chrome://crashes should show all the crashes.

What do you see instead?
chrome://crashes still say crash reporting disabled.

Please use labels and text to provide additional information.

Comment 1 by wnwen@chromium.org, Mar 31 2016

Labels: OS-Android
Status: Assigned (was: Untriaged)

Comment 2 by wnwen@chromium.org, Apr 4 2016

Cc: mlliu@chromium.org

Comment 3 by wnwen@chromium.org, Apr 4 2016 

Not sure, should this be fixed or should this follow the user checkbox? Since these cmdline flags are for testing automation with no UI, and chrome://crashes is UI, perhaps we shouldn't acknowledge commandline forcing flags.

When  http://crbug.com/599268  is fixed then we will be able to check the checkbox in local official builds.

Comment 4 by wnwen@chromium.org, May 3 2016

Status: WontFix (was: Assigned)
Since the checkbox is now available, marking this as obsolete.
►

Sign in to add a comment