Strictmode violation from Clear Browsing Data |
||
Issue descriptionThis crash occured while deleting data from CBD: crash/df169ba680f01a31 android.os.StrictMode$StrictModeDiskReadViolation: policy=16842815 violation=2 at android.os.StrictMode$AndroidBlockGuardPolicy.onReadFromDisk (StrictMode.java:1438 ) at java.io.UnixFileSystem.checkAccess (UnixFileSystem.java:251 ) at java.io.File.exists (File.java:1125 ) at android.app.ContextImpl.getDataDir (ContextImpl.java:2228 ) at android.content.ContextWrapper.getDataDir (ContextWrapper.java:222 ) at android.content.ContextWrapper.getDataDir (ContextWrapper.java:222 ) at android.app.EmbryoApp.isDataAccessable (EmbryoApp.java:95 ) at android.app.EmbryoApp.checkHWUI (EmbryoApp.java:105 ) at android.view.ThreadedRenderer.<init> (ThreadedRenderer.java:368 ) at android.view.ThreadedRenderer.create (ThreadedRenderer.java:266 ) at android.view.ViewRootImpl.enableHardwareAcceleration (ViewRootImpl.java:994 ) at android.view.ViewRootImpl.setView (ViewRootImpl.java:707 ) at android.view.WindowManagerGlobal.addView (WindowManagerGlobal.java:356 ) at android.view.WindowManagerImpl.addView (WindowManagerImpl.java:93 ) at android.app.Dialog.show (Dialog.java:330 ) at android.app.ProgressDialog.show (ProgressDialog.java:181 ) at android.app.ProgressDialog.show (ProgressDialog.java:155 ) at org.chromium.chrome.browser.preferences.privacy.ClearBrowsingDataPreferences.showProgressDialog (ClearBrowsingDataPreferences.java:644 ) at org.chromium.chrome.browser.preferences.privacy.ClearBrowsingDataPreferences.clearBrowsingData (ClearBrowsingDataPreferences.java:343 ) at org.chromium.chrome.browser.preferences.privacy.ClearBrowsingDataPreferences.onActivityResult (ClearBrowsingDataPreferences.java:718 ) at org.chromium.chrome.browser.preferences.privacy.ConfirmImportantSitesDialogFragment$1.onClick (ConfirmImportantSitesDialogFragment.java:305 )
,
Nov 7
I had 4 crashes simultaneously. One is related to feed (https://crbug.com/902123), the other three are strictmode violations (c413cfc72d7a140f, 7cf4f93c058fc724 and df169ba680f01a31). I'm not sure if the first crash caused the other three because I can't reproduce any of these crashes by deleting data again. I was signed in with an @managedchrome.com account
,
Nov 7
Strict mode violations aren't real crashes -- they're disk reads or writes on the UI thread. Sometimes inflating UI elements causes disk reads, which appears to be what's happening here. Sometimes we sweep these under the rug by temporarily allowing the strict mode violation. Often we just ignore these. It's possible to inflate UI on a background thread to avoid disk reads. Generally we treat these sort of strict mode violations as P3's -- not critical to address.
,
Nov 8
Ok, the crash signature only shows one crash that wasn't caused by me, so I will wait and see if I find a reproducable way to trigger this. |
||
►
Sign in to add a comment |
||
Comment 1 by dullweber@chromium.org
, Nov 7