New issue
Advanced search Search tips

Issue 649714 link

Starred by 2 users

Issue metadata

Status: Duplicate
Merged: issue 644450
Owner:
Closed: Oct 2016
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows , Mac
Pri: 1
Type: Bug-Regression



Sign in to add a comment

Browser Tab Freezing in 53.0.2785.116 on OS X

Reported by step...@theline.com, Sep 23 2016

Issue description

UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/53.0.2785.116 Safari/537.36

Steps to reproduce the problem:
1. visit https://www.theline.com/shop/fashion
2. click add to bag to add any product to bag. 
3. browser tab will freeze up (sometimes on first attempt. but always within less than 5 add to carts) 

What is the expected behavior?
post request to /orders/populate should return a json response which handlebars compiles into a mini cart / "this item has been successfully added to your cart" modal -- see behavior in another browser/version of chrome for an example

What went wrong?
the tab freezes, if left open without force quitting chrome, the processor begins to heat up and the computers' fans will turn on 

Crashed report ID: no

How much crashed? Just one tab

Is it a problem with a plugin? N/A 

Did this work before? Yes Previous versions of chrome

Chrome version: 53.0.2785.116  Channel: stable
OS Version: OS X 10.10.5
Flash Version: Shockwave Flash 23.0 r0

Google sheet of this bug occurring in this chrome version, across different OS's: https://docs.google.com/spreadsheets/d/1FRPNtwpNxY8MefDopI49HxfZnxwcc3kaofhVK1IcVIE/edit
 

Comment 1 by step...@theline.com, Sep 23 2016

Our temporary fix was to disable the crashing behavior if Javascript detected 53.0.2785.116 in the user agent string.  Therefore, when trying to reproduce this, PLEASE MAKE SURE TO CHANGE THE USER AGENT STRING TO SOMETHING ELSE. thanks.

Comment 2 by shrike@chromium.org, Sep 27 2016

Labels: Needs-Feedback
Unable to reproduce in 53.0.2785.116 and 55.0.2873.0.

Please send a crash id (chrome://crashes).

Comment 3 by shrike@chromium.org, Sep 27 2016

Sorry - you said the tab is freezing, not that you got a crash. What does "tab freezes" mean, exactly? Is the browser non-responsive?

Can you take a sample using chrome://tracing, and one using the JavaScript developer tools?

Comment 4 by step...@theline.com, Sep 27 2016

Thanks Shrike I'll get you that info.  Yes tab freeze means that the browser became unresponsive.  Also please see my comment with the note that we pushed a fix to our site that detects User Agent and handles traffic from Chrome 53.0.2785.116 differently.  Therefor to accurately reproduce, you may need to spoof the UA as something else.  It generally crashed around the time there was a CSS animation, fwiw.
Labels: Needs-Bisect
Was able to repro in 53.0.2785.116, but not in 55.0.2873.0 spoofing as a Nexus 7 (which is on Chrome 48) via Dev tools. Not sure how to use chrome:tracing, but if the default settings are fine (selected the 'Web Developer' checkbox), have attached a trace.

Specific repro instructions:
1. If on Chrome 53.0.2785.116, open DevTools and click the phone icon (second icon on top-right) and select the presets for a Nexus 7. Keep DevTools open as closing them will revert any changes to the UA string.
2. Click 'Add to Bag' on any product. A menu pops out from the right and the tab becomes non-responsive. Task manager shows the tab going up to ~100% CPU and it has to be killed manually.

Probably needs a bisect since it's working again in Chrome 55? Tagging with Needs-Bisect.
trace_theline-freeze.json.gz
7.7 MB Download
Status: Untriaged (was: Unconfirmed)
Components: Blink>Layout>Flexbox
Labels: -Type-Bug -Pri-2 -Needs-Feedback -Needs-Bisect has-Bisect M-54 OS-Linux OS-Windows Pri-1 Type-Bug-Regression
Owner: szager@chromium.org
Status: Assigned (was: Untriaged)
Able to reproduce the issue on Windows 10, Ubuntu 14.04, Mac OS 10.11.6 using chrome reported version #53.0.2785.116.

Reverse Bisect Information:
=====================
Good build: 54.0.2840.34
Bad Build : 54.0.2840.33

Change Log URL: 
https://chromium.googlesource.com/chromium/src/+log/54.0.2840.33..54.0.2840.34?pretty=fuller&n=10000

From the above change log suspecting below change

Review URL: https://codereview.chromium.org/2345103002

szager@ - Could you please check whether this is caused with respect to your change, if not please help us in assigning it to the right owner.

This is probably a duplicate of  crbug.com/644450 , which is now fixed in all branches.  This bug doesn't reproduce for me on ChromeOS running version 53.0.2785.129.

Please let me know if the problem is now fixed.
Thanks all.  I have not been able to reproduce in version 53.0.2785.143.  I think it is fixed and was indeed a duplicate of  crbug.com/644450 .
Mergedinto: 644450
Status: Duplicate (was: Assigned)

Sign in to add a comment