Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix: [#3215] Check shader complexity to avoid crash on certain hardware #3216

Merged
merged 3 commits into from
Sep 23, 2024

Conversation

eonarheim
Copy link
Member

===:clipboard: PR Checklist :clipboard:===

  • 📌 issue exists in github for these changes
  • 🔬 existing tests still pass
  • 🙈 code conforms to the style guide
  • 📐 new tests written and passing / old tests updated with new scenario(s)
  • 📄 changelog entry added (or not needed)

==================

Closes #3215

Changes:

  • Tests shader complexity starting with max texture slots

@github-actions github-actions bot added the bug This issue describes undesirable, incorrect, or unexpected behavior label Sep 23, 2024
Copy link

cloudflare-workers-and-pages bot commented Sep 23, 2024

Deploying excaliburjs with  Cloudflare Pages  Cloudflare Pages

Latest commit: e2455c0
Status: ✅  Deploy successful!
Preview URL: https://1f1b9489.excaliburjs.pages.dev
Branch Preview URL: https://fix-shader-complexity.excaliburjs.pages.dev

View logs

@eonarheim eonarheim merged commit f506da4 into main Sep 23, 2024
7 checks passed
@eonarheim eonarheim deleted the fix/shader-complexity branch September 23, 2024 14:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug This issue describes undesirable, incorrect, or unexpected behavior
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Error: Cannot build new ExcaliburGraphicsContext2D
1 participant