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

Issue 628978 link

Starred by 4 users
Status: Duplicate
Merged: issue 628525
Owner:
khmel@chromium.org
Closed: Aug 2016
Cc:
ajha@chromium.org
█ kavvaru@chromium.org
fukino@chromium.org
yawano@chromium.org
vsu...@chromium.org
songsuk@chromium.org
█ durga.behera@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug-Regression



Sign in to add a comment

Share overlay is crashing in Files.app

Project Member Reported by sandeepk...@techmahindra.com, Jul 18 2016 
Version: 54.0.2798.0/8601.0.0 (Official Build) dev-channel Gnawty, Wolf
OS: Chrome

What steps will reproduce the problem?
(1) Sign in to user>> go to Files.app>> create one folder>> Share the folder>> click on advanced>> Click in invite people edit box>> Click on add message>> try to do something on the Share overlay using touch pad>> and observe

Expected: Share overlay should not crash
Actual: Instead its crashing

This is a Regression issue as issue is not seen in M51: 51.0.2704.103/8172.60.0 -Stable-Channel Gnawty

Issue is not applicable to Linux and Windows

Issue is not seen in Falco with the same above mentioned version

Crash ID: fdc5f6f600000000
Actual.png
698 KB View Download

Comment 1 by ajha@chromium.org, Jul 18 2016

Cc: songsuk@chromium.org vsu...@chromium.org
Issue is reproducible on 54.0.2798.0/8601.0.0_Dev channel Falco.

Comment 2 by ajha@chromium.org, Jul 18 2016 

Stack trace of the above crash doesn't have any Debug symbol.

Stack trace of fdc5f6f600000000:
================================
Thread 0 CRASHED [SIGILL @ 0x00007f97725328b9 ] MAGIC SIGNATURE THREAD
0x00007f97725328b9	(chrome + 0x023328b9 )	
0x00007f9771873958	(chrome + 0x01673958 )	
0x00007f9770e6d21b	(chrome + 0x00c6d21b )	
0x00007f97706506ab	(chrome + 0x004506ab )	
0x00007f977065113a	(chrome + 0x0045113a )	
0x00007f97706526bb	(chrome + 0x004526bb )	
0x00007f97718cff1b	(chrome + 0x016cff1b )	
0x00007f97718ce000	(chrome + 0x016ce000 )	
0x00007f976f507578		
0x00007f976f4f3edd		
0x00007f976f4f4449		
0x00007f9771e7f947	(chrome + 0x01c7f947 )	
0x00007f9771e97408	(chrome + 0x01c97408 )	
0x00007f9771e9751f	(chrome + 0x01c9751f )	
0x00007f9771e95765	(chrome + 0x01c95765 )	
0x00007f976df82306	(libpthread-2.19.so -pthread_create.c:309 )	start_thread
0x00007f976cc9c5cc	(libc-2.19.so + 0x000f95cc )	clone

Comment 3 by yawano@chromium.org, Jul 19 2016

Cc: fukino@chromium.org

Comment 4 by fukino@chromium.org, Jul 19 2016

Cc: khmel@chromium.org
The issue looks similar to  Issue 615512 .

Comment 5 by xiy...@chromium.org, Jul 19 2016 

Suspect this is  issue 628525  too.

Please check if ui.LATEST has the following line when the crash happens. If so, let's merge it into  issue 628525 .

[1:3:0718/173324:FATAL:fling_curve.cc(48)] Check failed: max_start_velocity > 0 (0 vs. 0)

Comment 6 by yawano@chromium.org, Jul 20 2016 

For comment #5, I cannot find the line in ui.LATEST for this issue. This might be different issue.

Comment 7 by yawano@chromium.org, Jul 20 2016

Cc: -khmel@chromium.org yawano@chromium.org
Owner: khmel@chromium.org
khmel@: Could you take a look at this? This looks similar to  issue 625776 . Thank you!

Comment 8 by fukino@chromium.org, Aug 25 2016

Status: WontFix (was: Assigned)
I can not reproduce the issue on 54.0.2839.0/8739.0.0 dev-channel nyan_big
I guess the root cause is same as  issue 628525 .

Let me close this issue.

Comment 9 by fukino@chromium.org, Aug 25 2016

Mergedinto: 628525
Status: Duplicate (was: WontFix)
►

Sign in to add a comment