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

Issue 741031 link

Starred by 5 users
Status: WontFix
Owner: ----
Closed: Apr 2018
Cc:
ka...@chromium.org
sontis@chromium.org
█ helenzhang@chromium.org
█ rjahagir@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug



Sign in to add a comment

[Chell] Observed ChromeOS_ARC crash (pthread_kill-a32011f0)

Project Member Reported by pgangishetty@chromium.org, Jul 11 2017 
Chrome Version: 61.0.3154.0
OS: 9734.0.0 (Official Build) dev-channel chell


What steps will reproduce the problem?
(1)Sign in to Device
(2)Opens Chrome browser by default


What is the expected result?
No crash should be seen

What happens instead?
3 Crashes observed after each Signout/Signin & reboot

Please use labels and text to provide additional information.

Crash Report ID 958d0f4fb8000000 (Local Crash ID: ChromeOS_ARC)
Crash Report ID 6436dcbe40000000 (Local Crash ID: ChromeOS_ARC)
Crash Report ID 19e8dcbe40000000 (Local Crash ID: Chrome)

logs and screenshot attached.  

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

Comment 2 by pgangishetty@chromium.org, Jul 11 2017

Description: Show this description

Comment 3 by songsuk@chromium.org, Sep 15 2017 

Reproduce the crash on Chrome 62.0.3202.24/CrOS 9901.17.0 - Kefka
Crash ID : 4d8aa2076e6d254d

Comment 4 by pucchakayala@chromium.org, Sep 26 2017 

Able to reproduce the issue on 	9901.29.0/62.0.3202.31 - Squawks

Steps:
1. Had gMail & cnn page tabs opened in one window. 
2. chrome://crashes & CrOS Developer shell tabs opened in another window.
3. Had CandyCrush ARC application running.
4. Chrome crashed & suddenly kicked back to the OOBE page.
5. Logged in to the user account & Restore button is shown saying Chrome has crashed.

Crash Report ID 4a260fb0dbbac51b [ARC crash]
Crash Report ID 8699c412434cb225 [CrOS crash]

Comment 5 by ka...@chromium.org, Oct 5 2017

Components: -Internals>CrashReporting UI>Browser>Navigation Platform>Apps>ARC
Labels: Stability-Hang

Comment 6 by mkarkada@chromium.org, Oct 18 2017 

Observed this crash on M-63 dev build (10032.4.0/ 63.0.3239.7) after AU and Sign in.

Comment 7 by jgome...@chromium.org, Oct 19 2017 

also observed on 64.0.3242.0 canary / 10044.0.0 on Reef/electro

Comment 8 by abodenha@chromium.org, Oct 24 2017 

Looks like this might be triggering/related to  bug 777935

Comment 9 by josa...@chromium.org, Oct 31 2017

Owner: lhchavez@chromium.org
Status: Assigned (was: Untriaged)
Similar bug here: https://bugs.chromium.org/p/chromium/issues/detail?id=768326

Comment 10 by lhchavez@chromium.org, Oct 31 2017

Owner: ----
Status: Available (was: Assigned)
The ARC-specific crash has been fixed in the last week. The kernel crash is unrelated.

Comment 11 by krishna...@chromium.org, Nov 3 2017 

Issue 780338 has been merged into this issue.

Comment 12 by shahrnoosh@google.com, Jan 9 2018 

Is there any update on this bug? is this bug still relevant?

Comment 13 by bhthompson@google.com, Apr 3 2018

Status: WontFix (was: Available)
If the kernel crash still happens let us file another bug.
►

Sign in to add a comment