Infinite WebGL error loop freezes browser on /features/ai/github-app (when hardware acceleration is off)

[heznpc]

🏷️ Discussion Type

Bug

💬 Feature/Topic Area

Copilot in GitHub

Body

Hey everyone,

I recently visited the GitHub AI feature page (https://github.com/features/ai/github-app), and it completely froze my Chrome and slowed down my entire MacBook.

I checked the console and noticed it’s an issue with how the page handles WebGL when hardware acceleration is disabled. Instead of gracefully falling back to a static background when it fails to create a WebGL context, the Three.js script gets stuck in an infinite loop.

It spams the console with THREE.WebGLRenderer: Error creating WebGL context hundreds of times a second, which causes a massive CPU spike (Chrome CPU usage shot up over 120%).

To reproduce:

Turn off "Use graphics acceleration when available" in Chrome settings.

Go to the page and open DevTools.

I have attached a screen recording that captures the entire issue. It demonstrates the hardware acceleration toggle being off (my settings UI is in Korean, but it's the standard toggle), the console getting flooded with errors, the resulting CPU spike in Activity Monitor, and finally, the page rendering perfectly once acceleration is turned back on.

Bug.report.mp4

Might want to add a proper fallback here so it doesn't crash browsers for users who don't or can't use hardware acceleration. Thanks!

[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. ⭐