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

Issue 628137 link

Starred by 3 users
Status: Duplicate
Owner:
arthurso...@chromium.org
Closed: Jul 2016
Cc:
jkummerow@chromium.org
ricea@chromium.org
nyerramilli@chromium.org
hablich@chromium.org
adamk@chromium.org
█ msrchandra@chromium.org
alex...@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows , Mac
Pri: 1
Type: Bug-Regression



Sign in to add a comment

Regression:Webpage crashes after login into facebook.com

Reported by vku...@etouch.net, Jul 14 2016 
Chrome Version:54.0.2796.2 (Official Build)Revision 677b7ff9c1739954e09b0bea21d75cdd1911d062-refs/branch-heads/2796@{#3} (32/64-bit)
OS:Mac OS X(10.10.5, 10.11.4),Windows(7,8,10)

What steps will reproduce the problem?
(1)Launch chrome and navigate to https://www.facebook.com/
(2)Login with valid credentials and observe.


Actual:Webpage crashes after login into facebook.com
Crash ID 39fc5bf5-1788-4166-b4a7-22cfc0cd7676 (Server ID: f8261b0900000000)
Crash ID fa2020c5-bcf9-48e0-b00a-6e75ef4ba8dc (Server ID: 8466d70200000000)

Expected:Webpage should not crash after login into facebook.com

This is a regression issue broken in 'M54' and will soon update other info.

Comment 1 by vku...@etouch.net, Jul 14 2016

Cc: ricea@chromium.org alex...@chromium.org
Components: Blink>Loader
Labels: Stability-Crash hasbisect OS-Linux
Owner: arthurso...@chromium.org
Status: Assigned (was: Unconfirmed)
Correction:
Step 1:Freshly launch chrome browser and navigate to  https://www.facebook.com/
Step 2:Login with valid credentials and wait while the page is loading,observe

Manual regression range:
Good Build: 54.0.2794.0
Bad Build: 54.0.2795.0

CL:
https://chromium.googlesource.com/chromium/src/+log/54.0.2794.0..54.0.2795.0?pretty=fuller&n=10000
(Unable to narrow down the range using tool since getting all good builds)

Suspecting:405179,405163 or 405015 ?
Actual_Crash.mov
2.2 MB Download

Comment 2 by ricea@chromium.org, Jul 14 2016 

Since it's a v8 crash, I suspect one of the many v8 rolls in the range.

405015 makes no substantive changes in the renderer process and so is unlikely to be able to cause this crash.

Comment 3 by msrchandra@chromium.org, Jul 14 2016

Cc: jkummerow@chromium.org hablich@chromium.org adamk@chromium.org
Labels: ReleaseBlock-Dev
Providing Stack Trace for the Crash Id -- f8261b0900000000

Stack Trace ::
===============
Thread 0 CRASHED [EXCEPTION_ACCESS_VIOLATION_READ @ 0x00000000 ] MAGIC SIGNATURE THREAD
0x000007fed307de2c	(chrome_child.dll -isolate.cc:892 )	v8::internal::Isolate::MayAccess(v8::internal::Handle<v8::internal::Context>,v8::internal::Handle<v8::internal::JSObject>)
0x000007fed22bb6ff	(chrome_child.dll -builtins.cc:4737 )	v8::internal::`anonymous namespace'::CreateDynamicFunction
0x000007fed22bc589	(chrome_child.dll -builtins.cc:4849 )	v8::internal::Builtin_Impl_FunctionConstructor
0x000007fed22bc53a	(chrome_child.dll -builtins.cc:4846 )	v8::internal::Builtin_FunctionConstructor
0x0000030705f0616a		
0x000007fed228e3cf	(chrome_child.dll + 0x004be3cf )

Adding RB Label as this is a recent Regression. Please remove if it is not required.
Also Cc'ing v8 sheriffs as this is v8 related Crash.
Thank You.

Comment 4 by hablich@chromium.org, Jul 14 2016

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

Sign in to add a comment