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

Issue 767153 link

Starred by 1 user

Issue metadata

Status: Duplicate
Merged: issue 767423
Owner:
OOO until Feb 4th
Closed: Sep 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 3
Type: Bug

Blocking:
issue 765936



Sign in to add a comment

Investigate StrictMode issue in android.view.Choreographer.getInstance

Project Member Reported by wnwen@chromium.org, Sep 20 2017

Issue description

Context: https://bugs.chromium.org/p/chromium/issues/detail?id=765936#c7

Here is another stack trace from 
https://luci-milo.appspot.com/buildbot/tryserver.chromium.android/linux_android_rel_ng/386702

09-16 14:29:21.859 25286 25286 D StrictMode: StrictMode policy violation; ~duration=468 ms: android.os.StrictMode$StrictModeDiskReadViolation: policy=2911 violation=2
09-16 14:29:21.859 25286 25286 D StrictMode: 	at android.os.StrictMode$AndroidBlockGuardPolicy.onReadFromDisk(StrictMode.java:1135)
09-16 14:29:21.859 25286 25286 D StrictMode: 	at libcore.io.BlockGuardOs.open(BlockGuardOs.java:106)
09-16 14:29:21.859 25286 25286 D StrictMode: 	at libcore.io.IoBridge.open(IoBridge.java:393)
09-16 14:29:21.859 25286 25286 D StrictMode: 	at java.io.FileOutputStream.<init>(FileOutputStream.java:88)
09-16 14:29:21.859 25286 25286 D StrictMode: 	at java.io.FileOutputStream.<init>(FileOutputStream.java:73)
09-16 14:29:21.859 25286 25286 D StrictMode: 	at com.android.server.DropBoxManagerService.add(DropBoxManagerService.java:211)
09-16 14:29:21.859 25286 25286 D StrictMode: 	at android.os.DropBoxManager.addText(DropBoxManager.java:272)
09-16 14:29:21.859 25286 25286 D StrictMode: 	at com.android.server.am.ActivityManagerService$17.run(ActivityManagerService.java:10018)
09-16 14:29:21.859 25286 25286 D StrictMode: 	at com.android.server.am.ActivityManagerService.addErrorToDropBox(ActivityManagerService.java:10025)
09-16 14:29:21.859 25286 25286 D StrictMode: 	at com.android.server.am.ActivityManagerService.handleApplicationWtf(ActivityManagerService.java:9832)
09-16 14:29:21.859 25286 25286 D StrictMode: 	at com.android.internal.os.RuntimeInit.wtf(RuntimeInit.java:337)
09-16 14:29:21.859 25286 25286 D StrictMode: 	at android.util.Log$1.onTerribleFailure(Log.java:104)
09-16 14:29:21.859 25286 25286 D StrictMode: 	at android.util.Log.wtf(Log.java:293)
09-16 14:29:21.859 25286 25286 D StrictMode: 	at android.util.Slog.wtf(Slog.java:82)
09-16 14:29:21.859 25286 25286 D StrictMode: 	at com.android.server.am.ActiveServices.killServicesLocked(ActiveServices.java:2081)
09-16 14:29:21.859 25286 25286 D StrictMode: 	at com.android.server.am.ActivityManagerService.cleanUpApplicationRecordLocked(ActivityManagerService.java:12427)
09-16 14:29:21.859 25286 25286 D StrictMode: 	at com.android.server.am.ActivityManagerService.handleAppDiedLocked(ActivityManagerService.java:3606)
09-16 14:29:21.859 25286 25286 D StrictMode: 	at com.android.server.am.ActivityManagerService.appDiedLocked(ActivityManagerService.java:3751)
09-16 14:29:21.859 25286 25286 D StrictMode: 	at com.android.server.am.ActivityManagerService$AppDeathRecipient.binderDied(ActivityManagerService.java:1026)
09-16 14:29:21.859 25286 25286 D StrictMode: 	at android.os.BinderProxy.sendDeathNotice(BinderProxy.java:493)
09-16 14:29:21.859 25286 25286 D StrictMode: 	at dalvik.system.NativeStart.run(NativeStart.java)
09-16 14:29:21.859 25286 25286 D StrictMode: # via Binder call with stack:
09-16 14:29:21.859 25286 25286 D StrictMode: android.os.StrictMode$LogStackTrace
09-16 14:29:21.859 25286 25286 D StrictMode: 	at android.os.StrictMode.readAndHandleBinderCallViolations(StrictMode.java:1705)
09-16 14:29:21.859 25286 25286 D StrictMode: 	at android.os.Parcel.readExceptionCode(Parcel.java:1447)
09-16 14:29:21.859 25286 25286 D StrictMode: 	at android.os.Parcel.readException(Parcel.java:1416)
09-16 14:29:21.859 25286 25286 D StrictMode: 	at android.hardware.display.IDisplayManager$Stub$Proxy.getDisplayInfo(IDisplayManager.java:222)
09-16 14:29:21.859 25286 25286 D StrictMode: 	at android.hardware.display.DisplayManagerGlobal.getDisplayInfo(DisplayManagerGlobal.java:117)
09-16 14:29:21.859 25286 25286 D StrictMode: 	at android.view.Choreographer.getRefreshRate(Choreographer.java:181)
09-16 14:29:21.859 25286 25286 D StrictMode: 	at android.view.Choreographer.<init>(Choreographer.java:172)
09-16 14:29:21.859 25286 25286 D StrictMode: 	at android.view.Choreographer.<init>(Choreographer.java:72)
09-16 14:29:21.859 25286 25286 D StrictMode: 	at android.view.Choreographer$1.initialValue(Choreographer.java:98)
09-16 14:29:21.859 25286 25286 D StrictMode: 	at android.view.Choreographer$1.initialValue(Choreographer.java:91)
09-16 14:29:21.859 25286 25286 D StrictMode: 	at java.lang.ThreadLocal$Values.getAfterMiss(ThreadLocal.java:430)
09-16 14:29:21.859 25286 25286 D StrictMode: 	at java.lang.ThreadLocal.get(ThreadLocal.java:65)
09-16 14:29:21.859 25286 25286 D StrictMode: 	at android.view.Choreographer.getInstance(Choreographer.java:194)
09-16 14:29:21.859 25286 25286 D StrictMode: 	at org.chromium.ui.VSyncMonitor.<init>(VSyncMonitor.java:69)
09-16 14:29:21.859 25286 25286 D StrictMode: 	at org.chromium.ui.base.WindowAndroid.<init>(WindowAndroid.java:214)
09-16 14:29:21.859 25286 25286 D StrictMode: 	at org.chromium.ui.base.WindowAndroid.<init>(WindowAndroid.java:199)
09-16 14:29:21.859 25286 25286 D StrictMode: 	at org.chromium.ui.base.WindowAndroid.<init>(WindowAndroid.java:199)
09-16 14:29:21.859 25286 25286 D StrictMode: 	at org.chromium.ui.base.ActivityWindowAndroid.<init>(ActivityWindowAndroid.java:69)
09-16 14:29:21.859 25286 25286 D StrictMode: 	at org.chromium.ui.base.ActivityWindowAndroid.<init>(ActivityWindowAndroid.java:60)
09-16 14:29:21.859 25286 25286 D StrictMode: 	at org.chromium.chrome.browser.ChromeWindow.<init>(ChromeWindow.java:24)
09-16 14:29:21.859 25286 25286 D StrictMode: 	at org.chromium.chrome.browser.ChromeActivity.createWindowAndroid(ChromeActivity.java:306)
09-16 14:29:21.859 25286 25286 D StrictMode: 	at org.chromium.chrome.browser.init.AsyncInitializationActivity.onCreateInternal(AsyncInitializationActivity.java:278)
09-16 14:29:21.859 25286 25286 D StrictMode: 	at org.chromium.chrome.browser.init.AsyncInitializationActivity.onCreate(AsyncInitializationActivity.java:243)
09-16 14:29:21.859 25286 25286 D StrictMode: 	at android.app.Activity.performCreate(Activity.java:5231)
09-16 14:29:21.859 25286 25286 D StrictMode: 	at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1087)
09-16 14:29:21.859 25286 25286 D StrictMode: 	at android.support.test.runner.MonitoringInstrumentation.callActivityOnCreate(MonitoringInstrumentation.java:532)
09-16 14:29:21.859 25286 25286 D StrictMode: 	at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2148)
09-16 14:29:21.859 25286 25286 D StrictMode: 	at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2233)
09-16 14:29:21.859 25286 25286 D StrictMode: 	at android.app.ActivityThread.access$800(ActivityThread.java:135)
09-16 14:29:21.859 25286 25286 D StrictMode: 	at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1196)
09-16 14:29:21.859 25286 25286 D StrictMode: 	at android.os.Handler.dispatchMessage(Handler.java:102)
09-16 14:29:21.859 25286 25286 D StrictMode: 	at android.os.Looper.loop(Looper.java:136)
09-16 14:29:21.859 25286 25286 D StrictMode: 	at android.app.ActivityThread.main(ActivityThread.java:5001)
09-16 14:29:21.859 25286 25286 D StrictMode: 	at java.lang.reflect.Method

 

Comment 2 by wnwen@chromium.org, Sep 21 2017

Mergedinto: 767423
Status: Duplicate (was: Fixed)

Comment 3 by wnwen@chromium.org, Sep 21 2017

Tracked at  issue 767624 .

Comment 4 by wnwen@chromium.org, Sep 21 2017

Components: Test>Android
Project Member

Comment 5 by bugdroid1@chromium.org, Sep 21 2017

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/908f3f7144b2598348d33a668d494f85070bba41

commit 908f3f7144b2598348d33a668d494f85070bba41
Author: Peter Wen <wnwen@chromium.org>
Date: Thu Sep 21 22:54:55 2017

Android: Patch flaky tests due to strict mode

Android system is crashing due to StrictMode but we need to know the
underlying cause in order to understand why it is flaking. Disabling
StrictMode just for those code paths as the flakiness is unreliable and
hard to reproduce.

BUG= 767423 , 767153 , 767624 

Change-Id: I0ddcabd876bab99841487742f039cea920ea433d
Reviewed-on: https://chromium-review.googlesource.com/677226
Commit-Queue: Peter Wen <wnwen@chromium.org>
Reviewed-by: ccameron chromium <ccameron@chromium.org>
Reviewed-by: Eric Stevenson <estevenson@chromium.org>
Cr-Commit-Position: refs/heads/master@{#503595}
[modify] https://crrev.com/908f3f7144b2598348d33a668d494f85070bba41/ui/android/java/src/org/chromium/ui/base/WindowAndroid.java

Sign in to add a comment