Chrome Crash
Reported by
shiva...@samsung.com,
Jul 19 2017
|
||||
Issue descriptionSteps to reproduce the problem: 1. Preconditon : install SDS IAM&EMM apk from play store - QA_Field_ 01 Policy [Admin Portal] 1. Policies > Select Test Police > Mobile Device Polices > Samsung KNOX Workspace Settings > Container Settings > Enable Google Apps - Allow Google apps in the container(Yes) 2. Policies > Select Test Police > Mobile Device Polices > Samsung KNOX Workspace Settings > Container Settings > Application Settings - Applications that can install other applications(com.android.vending) Occurrence Process : [Device] Open knox-> chrome -> Browse anything -> Observe What is the expected behavior? chrome has been stopped should not occur . What went wrong? FATAL EXCEPTION: AsyncTask #5 07-14 15:26:36.190 17806 18304 E AndroidRuntime: Process: com.android.chrome, PID: 17806 07-14 15:26:36.190 17806 18304 E AndroidRuntime: java.lang.RuntimeException: An error occurred while executing doInBackground() 07-14 15:26:36.190 17806 18304 E AndroidRuntime: at android.os.AsyncTask$3.done(AsyncTask.java:325) 07-14 15:26:36.190 17806 18304 E AndroidRuntime: at java.util.concurrent.FutureTask.finishCompletion(FutureTask.java:354) 07-14 15:26:36.190 17806 18304 E AndroidRuntime: at java.util.concurrent.FutureTask.setException(FutureTask.java:223) 07-14 15:26:36.190 17806 18304 E AndroidRuntime: at java.util.concurrent.FutureTask.run(FutureTask.java:242) 07-14 15:26:36.190 17806 18304 E AndroidRuntime: at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1133) 07-14 15:26:36.190 17806 18304 E AndroidRuntime: at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:607) 07-14 15:26:36.190 17806 18304 E AndroidRuntime: at java.lang.Thread.run(Thread.java:762) 07-14 15:26:36.190 17806 18304 E AndroidRuntime: Caused by: java.lang.NullPointerException: Attempt to invoke virtual method 'boolean java.lang.String.isEmpty()' on a null object reference 07-14 15:26:36.190 17806 18304 E AndroidRuntime: at com.google.android.apps.chrome.policy.knoxsettings.KnoxAuditLogger$4.doInBackground(KnoxAuditLogger.java:1195) 07-14 15:26:36.190 17806 18304 E AndroidRuntime: at android.os.AsyncTask$2.call(AsyncTask.java:305) 07-14 15:26:36.190 17806 18304 E AndroidRuntime: at java.util.concurrent.FutureTask.run(FutureTask.java:237) Crashed report ID: 00891463 How much crashed? Whole browser Is it a problem with a plugin? No Did this work before? N/A Chrome version: 59 Channel: stable OS Version: Nougat Flash Version: Shockwave Flash 26.0 r0
,
Aug 10 2017
+bauerb Could you take a look as you recently work a lot with android/apps/chrome/policy/knoxsettings ? Seems crashes on line https://cs.corp.google.com/clank/java/src/com/google/android/apps/chrome/policy/knoxsettings/KnoxAuditLogger.java?q=KnoxAuditLogger.java&dr&l=195
,
Aug 11 2017
Oh hey, turns out we really do need non-null error descriptions (see issue 690784) :D
,
Aug 15 2017
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/81699cb2882e2b6f0becbdc308948fd56d5b7bbf commit 81699cb2882e2b6f0becbdc308948fd56d5b7bbf Author: Bernhard Bauer <bauerb@chromium.org> Date: Tue Aug 15 16:02:02 2017 [Android] Avoid null description strings in the policy audit logger. Add an assert to catch null values even if the audit logger is disabled (which is most of the time). Bug: 746174 Change-Id: Ie39ff0c9095bf7636ac03508c468080af2200253 Reviewed-on: https://chromium-review.googlesource.com/612241 Reviewed-by: Shakti Sahu <shaktisahu@chromium.org> Reviewed-by: Sami Kyöstilä <skyostil@chromium.org> Commit-Queue: Bernhard Bauer <bauerb@chromium.org> Cr-Commit-Position: refs/heads/master@{#494394} [modify] https://crrev.com/81699cb2882e2b6f0becbdc308948fd56d5b7bbf/chrome/android/java/src/org/chromium/chrome/browser/tab/TabWebContentsObserver.java [modify] https://crrev.com/81699cb2882e2b6f0becbdc308948fd56d5b7bbf/content/browser/android/web_contents_observer_proxy.cc
,
Aug 23 2017
Hello, Can you please update me, in which version of Chrome this fix will be integrated? Thanks!
,
Aug 23 2017
Probably in Chrome 62. |
||||
►
Sign in to add a comment |
||||
Comment 1 by rsgav...@chromium.org
, Jul 27 2017