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

[jabagawee]

🏷️ Discussion Type

Bug

Body

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]]

💬 Your Product Feedback Has Been Submitted 🎉

Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users.

Here's what you can expect moving forward ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities.

Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐