Releases pages keep hidden loading spinners animating, pinning a CPU core

[jabagawee]

On repos with a long releases list, the releases index page keeps Chrome busy indefinitely after load, even with the tab idle. The page re-renders continuously at ~70fps and for me Chrome's GPU process sits around half a core. Scrolling to the bottom once makes it drop to idle.

My best guess, taken from a DevTools performance trace: each release row has two lazy <include-fragment> elements (the expanded_assets list and the refs picker), and their placeholder spinners (svg.anim-rotate, with the infinite rotate-keyframes animation) keep animating while below the fold. Since the fragments don't load until scrolled into view, the spinners animate forever. Blink can't run transform animations on SVG targets on the compositor (the trace reports compositeFailed with kTransformRelatedPropertyCannotBeAcceleratedOnTarget), so every frame renders on the main thread. I think the fix would be to pause the animation when it's offscreen.

Steps to reproduce:

1. In Chrome, open a releases page with 10+ releases, e.g. https://github.com/jundot/omlx/releases
2. Don't scroll or interact with the page.
3. Watch Activity Monitor or Chrome's Task Manager: renderer and GPU process CPU stays elevated indefinitely. Scroll to the bottom of the page and it drops to idle.

Seen on Chrome 150.0.7871.129 on macOS 26.5.2 (Apple Silicon); reproduces in a clean guest profile. I tried filing this through the support bug-report form but was redirected here.

Extra question: why is this even dynamically loaded if the Releases page is not infinite scroll? Given that it's paginated, why not just load the entire page in the browser statically?

[github-actions[bot]]

Thank you for your interest in contributing to our community! We currently only accept discussions created through the GitHub UI using our provided discussion templates. Please re-submit your discussion by navigating to the appropriate category and using the template provided.

This discussion has been closed because it was not submitted through the expected format. If you believe this was a mistake, please reach out to the maintainers.

[jabagawee]

reposted as #202458 i guess