@pathirajarao: Please provide test URL on which you are seeing this issue along with device details and OS version? As per comment#0 this seems be desktop issue, Please let us know on which OS you are seeing this? Also you are using older version of chrome. Please upgrade chrome to latest stable and let us know if this issue is still seen.

@chelamcherla: this issue is not in desktop. This issue is seen in Android Mobile which running on Oreo 8.1. And the issue is seen in "Stability test".
Once we get the test url, will update/provide you the same.
We will check with latest stable version of chrome and will share you the update on issue.

Thank you for providing more feedback. Adding the requester to the cc list.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

@chelamcherla:
Observed Chrome crash during Stability test. And the issue is seen in Android device not Desktop.
Chrome_Android version:68.0.3440.91 

The reason for Chrome crash is
===============================

08-23 12:23:49.639 27760 27760 E AndroidRuntime: java.lang.RuntimeException: Error receiving broadcast Intent { act=android.net.conn.CONNECTIVITY_CHANGE flg=0x4000010 (has extras) } in org.chromium.net.NetworkChangeNotifierAutoDetect@b980bd2



For reference attaching the Crash0.txt.

Deleted: Crash0.txt 57.2 KB

Crash0.txt 57.2 KB View Download

@chelamcherla: Update of Chrome ANR.
Chrome ANR is seen in Stability test of Android mobile with Android verison 8.1(Oreo).
Chrome version: 68.0.3440.91

Here is the log snippet:
========================
JobServiceContext: Client timed out while executing (no jobFinished received), sending onStop: cb824b9 #u0a119/54 com.android.chrome/org.chromium.components.background_task_scheduler.BackgroundTaskJobService

JobServiceContext: No response from client for onStopJob cb824b9 #u0a119/54 com.android.chrome/org.chromium.components.background_task_scheduler.BackgroundTaskJobService

JobServiceContext: Time-out while trying to bind 2a2dbe2 #u0a119/54 com.android.chrome/org.chromium.components.background_task_scheduler.BackgroundTaskJobService, dropping.

ActivityManager: Timeout executing service: ServiceRecord{ede7195 u0 com.android.chrome/org.chromium.components.background_task_scheduler.BackgroundTaskJobService}

ActivityManager: ANR in com.android.chrome

ActivityManager: Reason: executing service com.android.chrome/org.chromium.components.background_task_scheduler.BackgroundTaskJobService

Killing 3688:com.android.chrome/u0a119 (adj 0): bg anr

-----------------------------------------------------------

ANR in com.android.chrome (com.android.chrome/com.google.android.apps.chrome.Main)

ActivityManager( 1280): Reason: Input dispatching timed out (Waiting to send key event because the focused window has not finished processing all of the input events that were previously delivered to it. Outbound queue length: 0. Wait queue length: 2.)

Deleted: bugreport.zip 5.4 MB

bugreport.zip 5.4 MB Download

+tguilbert in case this is casting related.

From a quick look at some of the crashes, nothing jumps out at me as casting specific. 

Not sure what the next steps would be here. 
Dale, could you help route it from here? Is there enough in the bugreport for anyone to work from? Thanks.

I think this is the same issue that we saw with a crazy CRL on the Apple site that Thomas was looking into. This should be resolved with the new remote playback stack which is now enable by default in 72.

Please reopen if you see this issue after 72.