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

Issue 622626 link

Starred by 0 users
Status: Duplicate
Merged: issue 622520
Owner:
wangxianzhu@chromium.org
Closed: Jun 2016
Cc:
ajha@chromium.org
█ kavvaru@chromium.org
rohi...@chromium.org
█ durga.behera@chromium.org
abod...@chromium.org
avkodipelli@chromium.org
█ mbarowsky+blinkimage@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug-Regression

Blocked on:
issue 610902


Sign in to add a comment

Regression: Tab is crashing on navigating to images in Amazon.com

Project Member Reported by sandeepk...@techmahindra.com, Jun 23 2016 
Version: 53.0.2773.0/8490.0.0 (Official Build) dev-channel Paine, Blaze, Gnawty, Peppy, Daisy
OS: Chrome
What steps will reproduce the problem?
(1)Sign in to user>> go to amazon.com>> try to select one product>> click on the thumbnails of the images

Expected: Tab should not crash
Actual: Instead tab is crashing 

This is a regression issue as it is working fine 52.0.2743.41/8350.31.0 beta channel daisy.

Issue is not seen in Linux 

Crash ID: ba5829e600000000

Comment 1 by sandeepk...@techmahindra.com, Jun 23 2016 

Attached video for the reference
Actual.webm
509 KB View Download

Comment 2 by kavvaru@chromium.org, Jun 23 2016

Status: Untriaged (was: Unconfirmed)
Able to reproduce the issue on Blaze using chrome version 

Stack trace
==================
Thread 0 CRASHED [SIGABRT @ 0x000003e800000001 ] MAGIC SIGNATURE THREAD
0x00007f48fd7a8b82	(libc-2.19.so -raise.c:56 )	raise
0x00007f48fd7aa89f	(libc-2.19.so -abort.c:89 )	abort
0x00007f49006f5474		
0x00007f49003424bb		
0x00007f490034314e		
0x00007f490450e183	(chrome + 0x0350e183 )	
0x00007f490206004b	(chrome + 0x0106004b )	
0x00007f490206002e	(chrome + 0x0106002e )	
0x00007f490206002e	(chrome + 0x0106002e )	
0x00007f490206002e	(chrome + 0x0106002e )	
0x00007f490206002e	(chrome + 0x0106002e )	
0x00007f4902063a05	(chrome + 0x01063a05 )	
0x00007f490206b672	(chrome + 0x0106b672 )	
0x00007f4902138f4e	(chrome + 0x01138f4e )	
0x00007f49019c54fa	(chrome + 0x009c54fa )	
0x00007f4902f29ce5	(chrome + 0x01f29ce5 )	
0x00007f490405a0c6	(chrome + 0x0305a0c6 )	
0x00007f4904060855	(chrome + 0x03060855 )	
0x00007f48ffe1c808		
0x00007f490036ab9c		
0x00007f48ffe1c808		
0x00007f48ffe07b49		
0x00007f48ffe08389		
0x00007f490071dbf7		
0x00007f49007077a8		
0x00007f4902e94ee5	(chrome + 0x01e94ee5 )	
0x00007f49006cb3cf		
0x00007f49006cb640		
0x00007f49006ca11a		
0x00007f490037079e		
0x00007f48fd793fb5	(libc-2.19.so -libc-start.c:292 )	__libc_start_main
0x00007f49003705fe

Comment 3 by abodenha@chromium.org, Jun 23 2016

Blockedon: 610902
Crash server is failing to symbolize crashes due to  bug 610902 . That's making it really hard to investigate stuff like this.

Comment 4 by avkodipelli@chromium.org, Jun 28 2016

Cc: abod...@chromium.org rohi...@chromium.org
Components: -UI Blink>Image
Labels: -ReleaseBlock-Beta ReleaseBlock-Dev
This issue also observed on 53.0.2773.0/8508.0.0. Crash iD's are b1d2969600000000, aded969600000000

Comment 5 by avkodipelli@chromium.org, Jun 28 2016

Cc: avkodipelli@chromium.org

Comment 6 by schenney@chromium.org, Jun 28 2016

Components: Internals>Compositing>Images
Given this is ChromeOS only, I have to think it's related to the compositor internals, or maybe Skia.

I can't find the crash IDs in comment #4.

Comment 8 by schenney@chromium.org, Jun 28 2016

Components: -Internals>Compositing>Images
Owner: wangxianzhu@chromium.org
Status: Assigned (was: Untriaged)
Assigning to wangxianzhu, as the crashes in the latest reports are in subsequence caching.

Comment 9 by wangxianzhu@chromium.org, Jun 28 2016

Mergedinto: 622520
Status: Duplicate (was: Assigned)
►

Sign in to add a comment