New issue
Advanced search Search tips

Issue 777340 link

Starred by 2 users
Status: WontFix
Owner: ----
Closed: Nov 14
Cc:
boliu@chromium.org
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 3
Type: Bug



Sign in to add a comment

[Restrict-View-Google] Error when running notes in the secure folder

Project Member Reported by twinkl...@samsung.com, Oct 23 2017 
Chrome Version: 60.x
OS: Android N-OS
Device: G930K

What steps will reproduce the problem?
(1)Operate memo app in the secure folder.

What is the expected result?
There should be no crash

What happens instead?
Memo app doesn't operate as the device stops due to crash.
 

For graphics-related bugs, please copy/paste the contents of the about:gpu
page at the end of this report.
dumpState_1503558754091.zip
6.5 MB Download

Comment 1 by twinkl...@samsung.com, Oct 23 2017 

08-24 16:11:55.491 23157 23195 E AndroidRuntime: FATAL EXCEPTION: Chrome_ProcessLauncherThread
08-24 16:11:55.491 23157 23195 E AndroidRuntime: Process: com.samsung.android.app.memo, PID: 23157
08-24 16:11:55.491 23157 23195 E AndroidRuntime: java.lang.RuntimeException: Could not get application info.
08-24 16:11:55.491 23157 23195 E AndroidRuntime:    at org.chromium.content.browser.ChildConnectionAllocator.create(ChildConnectionAllocator.java:11)
08-24 16:11:55.491 23157 23195 E AndroidRuntime:    at org.chromium.content.browser.ChildProcessLauncher.getConnectionAllocator(ChildProcessLauncher.java:21)
08-24 16:11:55.491 23157 23195 E AndroidRuntime:    at org.chromium.content.browser.ChildProcessLauncher.allocateBoundConnection(ChildProcessLauncher.java:48)
08-24 16:11:55.491 23157 23195 E AndroidRuntime:    at org.chromium.content.browser.ChildProcessLauncher$1.allocateBoundConnection$5166USJ75THMGSJFDLKNAR9FCDNMST35DPQ2UOJIDTRN6PBI5T1MGQBCCH9N0OBNDP262T317D66USJ75THMGSJFDLKNAR9FCDNMST35DPQ2UOJIDTRN6PBI5T1MGQBCCH874RR3CLPN6GRFDPN6AORKD5NMS92JEHGN4T23C5M6OOJ1CDLJMMH99HNN4PPFCDK74RRDD5QMQBR3DTN78PBEEGNM4SJFETPMASHF8DK6IR34A1P6UOR5EDPK6RREDPIM6T39DTN3M___0(ChildProcessLauncher.java:2)
08-24 16:11:55.491 23157 23195 E AndroidRuntime:    at org.chromium.content.browser.SpareChildConnection.<init>(SpareChildConnection.java:6)
08-24 16:11:55.491 23157 23195 E AndroidRuntime:    at org.chromium.content.browser.ChildProcessLauncher$7.run(ChildProcessLauncher.java:11)
08-24 16:11:55.491 23157 23195 E AndroidRuntime:    at android.os.Handler.handleCallback(Handler.java:751)
08-24 16:11:55.491 23157 23195 E AndroidRuntime:    at android.os.Handler.dispatchMessage(Handler.java:95)
08-24 16:11:55.491 23157 23195 E AndroidRuntime:    at android.os.Looper.loop(Looper.java:154)
08-24 16:11:55.491 23157 23195 E AndroidRuntime:    at android.os.HandlerThread.run(HandlerThread.java:61)

Comment 2 by mili.adl...@samsung.com, Dec 26 2017 

Can we get an update on this issue?

Comment 3 by shiva...@samsung.com, Feb 23 2018 

We have observed the same issue on latest Chrome version as well.
Any update on this ?

Comment 4 by dtapu...@chromium.org, Oct 29

Labels: Needs-Feedback
Still occurring or this issue stle?

Comment 5 Deleted

Comment 6 by twinkl...@samsung.com, Nov 9 

Similar Crash is reproducible to us on launch of chrome app in SM-N960N. The device details are as below:

Model:    N960N
Chrome Version:   70.0.3538.80
Android:   P-OS

Dumpstate has been attached for reference.
dumpState_N960NKSU2CRK1_201811070831.zip
6.8 MB Download

Comment 7 by tedc...@chromium.org, Nov 14

Cc: boliu@chromium.org
+boliu for a quick glance, but this has the smell of a framework change messing with how we launch processes:

That looks like a different bug or at least the stack seems different:
11-07 08:29:44.641 10122  8786  8842 E AndroidRuntime: FATAL EXCEPTION: Chrome_ProcessLauncherThread
11-07 08:29:44.641 10122  8786  8842 E AndroidRuntime: Process: com.android.chrome, PID: 8786
11-07 08:29:44.641 10122  8786  8842 E AndroidRuntime: java.lang.RuntimeException: Illegal meta data value: the child service doesn't exist
11-07 08:29:44.641 10122  8786  8842 E AndroidRuntime: 	at aqk.a(SourceFile:15)
11-07 08:29:44.641 10122  8786  8842 E AndroidRuntime: 	at org.chromium.content.browser.ChildProcessLauncherHelperImpl.a(SourceFile:52)
11-07 08:29:44.641 10122  8786  8842 E AndroidRuntime: 	at bKh.run(SourceFile:6)
11-07 08:29:44.641 10122  8786  8842 E AndroidRuntime: 	at android.os.Handler.handleCallback(Handler.java:873)
11-07 08:29:44.641 10122  8786  8842 E AndroidRuntime: 	at android.os.Handler.dispatchMessage(Handler.java:99)
11-07 08:29:44.641 10122  8786  8842 E AndroidRuntime: 	at android.os.Looper.loop(Looper.java:206)
11-07 08:29:44.641 10122  8786  8842 E AndroidRuntime: 	at android.os.HandlerThread.run(HandlerThread.java:65)

Comment 8 by boliu@chromium.org, Nov 14

Status: WontFix (was: Untriaged)
Your OS is breaking fundamental android APIs here. Chrome is trying to talk to its own external and exported service. There is no reason that should ever fail.
►

Sign in to add a comment