New issue
Advanced search Search tips

Issue 648660 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner: ----
Closed: Oct 2016
Components:
EstimatedDays: ----
NextAction: ----
OS: Mac
Pri: 2
Type: Bug



Sign in to add a comment

Animations drop frames when debugging with inspector since the last Chrome update

Reported by daronale...@gmail.com, Sep 20 2016

Issue description

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

Steps to reproduce the problem:
1. Visit page with animations (developed using Greensocks library)
2. Open the inspector
3.

What is the expected behavior?
Since the update to 53.0.2785.116 (64-bit) the animation is really choppy especially when I have the inspector open.

I'm working on an animation which ran beautifully smooth during all other updates. I'm using 3 (Greensock) timelines to animate a character.

The character is svg based and starts in a neural position. I animate head rocking which is accomplished by:

1. Setting the transformOrigin and rotating the head to extreme left.I set a keyframe here

2. At a few seconds into the animation I set the head to be rotated to the opposite extreme and set another keyframe.

3. At the equal duration to the previous keyframe I rotate the head back to the negative extreme (meaning it's back at it's start point).

What went wrong?
Prior to this update the head rotated left to right smoothly without any jank.

Since the update the animation appears to reset to the loaded in state at the end of every cycle without animation. So it animates 1-3 the to neutral making the head rocking really ugly and freaky!

It works as intended 1 in 15ish refreshes and works in Chrome Canary (and Firefox - just really laggy)

Did this work before? Yes Prior to the update

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

I suspect that something in the new inspector animation tools is affecting the animations
 
My bad. This was caused by me attaching the timeline to angular scope. Possibly Angular event loop fighting with greensocks own. Issue is resolved.

Comment 2 by alph@chromium.org, Oct 10 2016

Status: WontFix (was: Unconfirmed)
Ok, closing it. Thanks for the heads up.

Sign in to add a comment