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

Issue 745328 link

Starred by 3 users
Status: WontFix
Owner: ----
Closed: Jul 2017
Cc:
pdr@chromium.org
chrishtr@chromium.org
█ wkorman@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug



Sign in to add a comment

Setting Animation playbackRate on a finished animation causes renderer crash.

Project Member Reported by dpa...@chromium.org, Jul 18 2017 
Reproduced on Linux 59.0.3071.115. Have not tried other platforms.

Minimal repro https://jsfiddle.net/90hva9jq/13/

Repro steps: Play an animation, wait until it finishes, set playbackRatio to -1, observe renderer crash. Does not happen on Firefox.

Notice that the crash does not happen if the playbackRate is set while animation has not finished yet.

Comment 1 by dpa...@chromium.org, Jul 18 2017

Labels: Stability-Crash

Comment 2 by dpa...@chromium.org, Jul 18 2017 

Example crash IDs, f821a39e78000000 and 41a1a39e78000000.

Comment 3 by dpa...@chromium.org, Jul 18 2017 

FYI, same crash seems to have been reported at issue 722731 (although that bug does not have repro steps).

Comment 4 by dpa...@chromium.org, Jul 18 2017

Components: Internals>Skia

Comment 5 by dpa...@chromium.org, Jul 18 2017

Summary: Setting Animation playbackRate on a finished animation causes renderer crash. (was: Setting playbackRate on a finished animation causes renderer crash.)

Comment 6 by dpa...@chromium.org, Jul 18 2017

Cc: chrishtr@chromium.org pdr@chromium.org wkorman@chromium.org
Labels: M-59
This seems fixed in ToT. Bisection revealed the following range

https://chromium.googlesource.com/chromium/src/+log/1c7e4324cc1c6e37212c0e8ac667c7d79b3947c5..18fc5e473594ff6bb062183835a60257def9a627

From which the most likely candidate is r473085.

Comment 7 by dpa...@chromium.org, Jul 18 2017 

Issue 722731 has been merged into this issue.

Comment 8 by chrishtr@chromium.org, Jul 19 2017

Status: WontFix (was: Untriaged)
Nice! My patch fixed another similar bug, so not surprising.
►

Sign in to add a comment