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

Issue 679787 link

Starred by 5 users
Status: Verified
Owner:
█ reve...@chromium.org
Last visit > 30 days ago
Closed: Jan 2017
Cc:
█ lhchavez@chromium.org
loyso@chromium.org
drinkcat@chromium.org
ka...@chromium.org
sdantul...@chromium.org
elijahtaylor@chromium.org
█ reve...@chromium.org
█ yoshiki@chromium.org
tfiga@chromium.org
dhadd...@chromium.org
osh...@chromium.org
abod...@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug



Sign in to add a comment

Playstore Crashes continously on TOT

Project Member Reported by rookrishna@chromium.org, Jan 10 2017 
 R57 TOT(9169.0.0 / 57.0.2977.0) samus

Please specify Cr-* of the system to which this bug/feature applies (add
the label below).

Steps To Reproduce:
(1) Update the device to TOT build
(2)Click on the playstore icon
(3)

Expected Result: No Crash

Actual Result:Crash

How frequently does this problem reproduce? (Always, sometimes, hard to
reproduce?)
Always to TOT signout and sign in does not fix the issue

What is the impact to the user, and is there a workaround? If so, what is
it?

Please provide any additional information below. Attach a screen shot or
log if possible.

For graphics-related bugs, please copy/paste the contents of the about:gpu
page at the end of this report.
logcat (4).txt
307 KB View Download

Comment 1 by rookrishna@chromium.org, Jan 10 2017 

Crash ID -  4514ffd080000000

		
0x00006209f986602b	(chrome -callback.h:85 )	gpu::CommandBufferProxyImpl::OnUpdateVSyncParameters(base::TimeTicks, base::TimeDelta)
0x00006209f9869cfc	(chrome -tuple.h:91 )	gpu::CommandBufferProxyImpl::OnMessageReceived(IPC::Message const&)
0x00006209f93f861c	(chrome -callback.h:68 )	base::debug::TaskAnnotator::RunTask(char const*, base::PendingTask*)
0x00006209f93e0a81	(chrome -message_loop.cc:421 )	base::MessageLoop::DoWork()
0x00006209f93e10d2	(chrome -message_pump_libevent.cc:218 )	base::MessagePumpLibevent::Run(base::MessagePump::Delegate*)
0x00006209fad4e437	(chrome -run_loop.cc:37 )	base::RunLoop::Run()
0x00006209faa31775	(chrome -chrome_browser_main.cc:1989 )	ChromeBrowserMainParts::MainMessageLoopRun(int*)
0x00006209fa07412a	(chrome -browser_main_loop.cc:1171 )	content::BrowserMainLoop::RunMainMessageLoopParts()
0x00006209fa077044	(chrome -browser_main_runner.cc:141 )	content::BrowserMainRunnerImpl::Run()
0x00006209fa0712fb	(chrome -browser_main.cc:46 )	content::BrowserMain(content::MainFunctionParams const&)
0x00006209fa9d1e99	(chrome -content_main_runner.cc:793 )	content::ContentMainRunnerImpl::Run()
0x00006209fa9d0b3a	(chrome -content_main.cc:20 )	content::ContentMain(content::ContentMainParams const&)
0x00006209f966901a	(chrome -chrome_main.cc:112 )	ChromeMain
0x0000746ec26bd795	(libc-2.23.so -libc-start.c:289 )	__libc_start_main
0x00006209f9668e48	(chrome + 0x011fae48 )	_start
0x00007ffe5d7648c7

Comment 2 by rookrishna@chromium.org, Jan 10 2017

Owner: elijahtaylor@chromium.org

Comment 3 by rookrishna@chromium.org, Jan 10 2017

log-011017-113431.tar.gz
3.4 MB Download

Comment 4 by elijahtaylor@chromium.org, Jan 11 2017

Cc: elijahtaylor@chromium.org
Owner: marc...@chromium.org
Status: Assigned (was: Untriaged)
Stephan, do you know who could take a look at this?  We're seeing this on M and N builds on samus (not sure about other devices), but it doesn't seem Android specific since it's in the GPU process.  This is a really bad blocker for ARC.

Comment 5 by rookrishna@chromium.org, Jan 11 2017 

Tested on Chell device too. Its the same Also the same crash occurs with  www.ndtv.com always on this build.

Comment 6 by marc...@chromium.org, Jan 11 2017

Owner: reve...@chromium.org
reveman@ is the best contact for chrome crashes

Comment 7 by reve...@chromium.org, Jan 11 2017 

This one should be fixed once https://codereview.chromium.org/2627713004 lands.
Project Member

Comment 8 by bugdroid1@chromium.org, Jan 11 2017 

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/b622b0bbb1c98da5d7ce4b9e7749698959b93fa1

commit b622b0bbb1c98da5d7ce4b9e7749698959b93fa1
Author: reveman <reveman@chromium.org>
Date: Wed Jan 11 21:52:48 2017

exo: Make sure vsync observer is removed when Surface is destroyed.

If the window is still in the tree when Surface is destroyed
then we need to remove the vsync observer in the dtor.

BUG= 679787 

Review-Url: https://codereview.chromium.org/2627713004
Cr-Commit-Position: refs/heads/master@{#442996}

[modify] https://crrev.com/b622b0bbb1c98da5d7ce4b9e7749698959b93fa1/components/exo/surface.cc

Comment 9 by reve...@chromium.org, Jan 11 2017

Status: Fixed (was: Assigned)

Comment 10 by reve...@chromium.org, Jan 17 2017

Cc: reve...@chromium.org lhchavez@chromium.org tfiga@chromium.org drinkcat@chromium.org loyso@chromium.org yoshiki@chromium.org osh...@chromium.org
 Issue 681730  has been merged into this issue.

Comment 11 by hennessywill@chromium.org, Jan 19 2017 

We just spotted this issue again on 9197 reef build.

Hoping it's in the logs here:  https://feedback.corp.google.com/product/208/neutron?lView=rd&lReport=51827636795

Comment 12 Deleted

Comment 13 by hennessywill@chromium.org, Jan 19 2017 

attaching sys logs
system_logs.txt
7.8 MB View Download

Comment 14 by tey060...@gmail.com, Jan 19 2017 

ช

เมื่อ 17 ม.ค. 2017 7:55 หลังเที่ยง "reve… via monorail" <
monorail+v2.2280869647@chromium.org> เขียนว่า

Comment 15 by elijahtaylor@chromium.org, Jan 19 2017 

I don't think this is the same root cause.  I will follow up with Will off-bug.

Comment 16 by rookrishna@chromium.org, Jan 20 2017

Status: Verified (was: Fixed)
Verified on 57.0.2984.0/9199.0
►

Sign in to add a comment