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

Issue 774444 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner: ----
Closed: Mar 2018
Cc:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 2
Type: Bug



Sign in to add a comment

Facebook force close after log in 2nd account

Reported by ruch...@samsung.com, Oct 13 2017

Issue description

Steps to reproduce the problem:
1. Open Setting
2. advanced Feature
3. enable Dual Facebook 
4. Log in 2nd Account
5. Observe 

What is the expected behavior?
There should not be any Force close.

What went wrong?
Force close occurred when try to login FB using 2nd account.

Did this work before? N/A 

Chrome version: 61.0.3163.100  Channel: stable
OS Version: 7.2
Flash Version:
 
dumpState_A530FXXU0AQID_201710031436.zip
4.7 MB Download

Comment 1 by ruch...@samsung.com, Oct 13 2017

10-03 14:36:20.732 12422 12722 E AndroidRuntime: FATAL EXCEPTION: Chrome_ProcessLauncherThread
10-03 14:36:20.732 12422 12722 E AndroidRuntime: Process: com.facebook.katana, PID: 12422
10-03 14:36:20.732 12422 12722 E AndroidRuntime: java.lang.SecurityException: BIND_EXTERNAL_SERVICE required for ComponentInfo{com.android.chrome/org.chromium.content.app.SandboxedProcessService0}
10-03 14:36:20.732 12422 12722 E AndroidRuntime:    at android.os.Parcel.readException(Parcel.java:1704)
10-03 14:36:20.732 12422 12722 E AndroidRuntime:    at android.os.Parcel.readException(Parcel.java:1654)
10-03 14:36:20.732 12422 12722 E AndroidRuntime:    at android.app.ActivityManagerProxy.bindService(ActivityManagerNative.java:5179)
10-03 14:36:20.732 12422 12722 E AndroidRuntime:    at android.app.ContextImpl.bindServiceCommon(ContextImpl.java:1533)
10-03 14:36:20.732 12422 12722 E AndroidRuntime:    at android.app.ContextImpl.bindService(ContextImpl.java:1492)
10-03 14:36:20.732 12422 12722 E AndroidRuntime:    at android.content.ContextWrapper.bindService(ContextWrapper.java:711)
10-03 14:36:20.732 12422 12722 E AndroidRuntime:    at android.content.ContextWrapper.bindService(ContextWrapper.java:711)
10-03 14:36:20.732 12422 12722 E AndroidRuntime:    at org.chromium.content.browser.ChildProcessConnectionImpl$ChildServiceConnection.bind(ChildProcessConnectionImpl.java:28)
10-03 14:36:20.732 12422 12722 E AndroidRuntime:    at org.chromium.content.browser.ChildProcessConnectionImpl.start(ChildProcessConnectionImpl.java:51)
10-03 14:36:20.732 12422 12722 E AndroidRuntime:    at org.chromium.content.browser.ChildProcessLauncher.allocateBoundConnection(ChildProcessLauncher.java:53)
10-03 14:36:20.732 12422 12722 E AndroidRuntime:    at org.chromium.content.browser.ChildProcessLauncher$3.run(ChildProcessLauncher.java:11)
10-03 14:36:20.732 12422 12722 E AndroidRuntime:    at android.os.Handler.handleCallback(Handler.java:751)
10-03 14:36:20.732 12422 12722 E AndroidRuntime:    at android.os.Handler.dispatchMessage(Handler.java:95)
10-03 14:36:20.732 12422 12722 E AndroidRuntime:    at android.os.Looper.loop(Looper.java:154)
10-03 14:36:20.732 12422 12722 E AndroidRuntime:    at android.os.HandlerThread.run(HandlerThread.java:61)
Labels: Needs-triage-Mobile
Cc: msrchandra@chromium.org rbasuvula@chromium.org nyerramilli@chromium.org sandeepkumars@chromium.org
Labels: Needs-Feedback
@ruchi.k -- Thank You for the report.
Could you please provide us device details and also it would be helpful if you also provide a screen cast of the issue for further triaging.
Thanks in Advance.

Comment 4 by caseq@chromium.org, Oct 17 2017

Components: -Platform>DevTools
Status: WontFix (was: Unconfirmed)
***Bulk Edit***

There is no valid investigation in the bug, closing. Feel free to reopen if needed.

Sign in to add a comment