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

Issue 687297 link

Starred by 1 user
Status: Fixed
Owner: ----
Closed: Feb 2017
Cc:
█ wnwen@chromium.org
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

Constantly crashing with StrictModeViolation errors

Project Member Reported by awdf@chromium.org, Jan 31 2017 
Chrome Version: 55.0, 56, 57 (maybe earlier)
OS: Android

What steps will reproduce the problem?
On 55, open Settings from the hamburger menu
On 56/57, just launch Chrome

What is the expected result?
No crash

What happens instead?
Crash every time
settings-crash.mp4
29.5 MB Download
settings_crash_error_log.txt
720 KB View Download
chromium_settings_crash_debug_log.txt
2.1 KB View Download

Comment 1 by awdf@chromium.org, Feb 3 2017

Cc: wnwen@chromium.org
Summary: Constantly crashing with StrictModeViolation errors (was: StrictMode crash when I open Settings on M55 & on startup on 56/57)
..And now it crashes on launch every time on 55 with StrictModeViolations .

I'm on a userdebug build of Android N, but this is the system-image installed version of Chrome, updated to 55 via the Play store, not a debug build, so I don't understand why it is crashing. (Maybe some flag I've set on my device? 'Show StrictMode violations' is not checked in developer options though..)

Comment 2 by wnwen@chromium.org, Feb 6 2017 

Can you check your command-line flags? You might have --strict-mode flag turned on in command line. You can use build/android/adb_chrome_public_command_line to check.

Comment 3 by awdf@chromium.org, Feb 6 2017

Status: Fixed (was: Untriaged)
Indeed yes that outputs ... "--strict-mode=testing" - and clearing it with build/android/adb_chrome_public_command_line '' fixed the crashes :) thanks!

Still don't know how I got into that state though.. perhaps from running the tests? or maybe I set it once and forgot about it.

Anyway, thanks! And hopefully this ticket helps anybody else that gets into this state.

Comment 4 by wnwen@chromium.org, Feb 6 2017 

Running instrumentation tests does indeed add the flag. Unfortunately on N the bot has the flag turned off for now (due to the same crashes that we haven't gotten around to fixing/whitelisting).
►

Sign in to add a comment