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

Issue 639637 link

Starred by 5 users
Status: WontFix
Owner:
█ victorhsieh@chromium.org
Last visit > 30 days ago
Closed: Oct 2016
Cc:
█ ivanpe@chromium.org
█ victorhsieh@chromium.org
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 3
Type: Bug

Blocked on:
issue 641188


Sign in to add a comment

Chrome crashed while submitting crash report for Play Services

Project Member Reported by w...@chromium.org, Aug 20 2016 
<b>Version: <Kenneth, what is the frequency?></b>
<b>OS: <please tell me it's not XP></b>

What steps will reproduce the problem?
(1) Sign-in to ChromeOS w/ ARC enabled.
(2) When Play Services crashes, click "Report" to report the issue.
(3) Enter a description and hit Send Report.

What is the expected output?

Expect that report is sent.

What do you see instead?

Chrome crashes when you hit Send Report.  See crash 603df94e00000000.

Comment 1 by uekawa@chromium.org, Aug 21 2016

Cc: victorhsieh@chromium.org

gms crashes with:
android.database.sqlite.SQLiteDatabaseLockedException: database is locked (code 5): , while compiling: PRAGMA journal_mode

It seems like this crash happens on pixel C too, so not ARC++ specific.

Comment 2 by uekawa@chromium.org, Aug 22 2016 

filed b/30997294

Comment 3 by victorhsieh@chromium.org, Aug 30 2016

Owner: victorhsieh@chromium.org
Status: Assigned (was: Untriaged)
This is fixed in the upcoming Play Services release.  We can also put the release in our image when ready.

Comment 4 by w...@chromium.org, Aug 30 2016 

Re #3: The bug I reported is that the whole of ChromeOS crashed when I hit the Send Report button, not the fact that Play Services itself happened to crash.

Comment 5 by victorhsieh@chromium.org, Aug 30 2016 

Crash 603df94e00000000 only presents Android process crash.  So I'm afraid there is not enough information to look into.  Is it still reproducible to you?

Comment 6 by w...@chromium.org, Aug 30 2016 

Corresponding crash Id for Chrome is 2ae3f94e00000000, but that has bogus
symbols due to issue 641188.

Comment 7 by w...@chromium.org, Aug 30 2016

Cc: ivanpe@chromium.org

Comment 8 by victorhsieh@chromium.org, Aug 30 2016

Blockedon: 641188

Comment 9 by uekawa@chromium.org, Aug 30 2016 

there was a chrome crash for a ARC window close, that might be it.
fixed on 54.0.2837.0/8737.0.0

Comment 10 by victorhsieh@chromium.org, Oct 17 2016

Status: WontFix (was: Assigned)
Please reopen if this is still reproducible.
►

Sign in to add a comment