Closed bramus closed 1 year ago
It took some time to investigate, but the reported error in the console is unrelated to the crash (See crbug/1340647). The connections between the DevTools pane and Content Script work fine, and don’t catch any errors at all.
Turns out it is a GPU crash in Chrome itself. When updating the currentTime
of the cloned animations in the extension, the extension crashes when doing that too fast after each other.
Inspecting the crash data crash/d4adab2203e014bd (Google internal only link), the CL that caused this change most likely is https://chromium-review.googlesource.com/c/chromium/src/+/4850750. Thankfully a revert CL https://chromium-review.googlesource.com/c/chromium/src/+/4862648 got merged today, so it should be fixed in tomorrow’s Canary build. Fingers crossed … 🤞
Verified fixed in Chrome 119.0.6008.0. Closing and updating labels.
When using the extension in current Chrome Canary (tested in Chrome 119.0.6005.0), the extension crashes when inspecting an element that has a Scroll-Driven Animation attached.
In the console, it reads this: