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

Website https://www.cogentcore.org/core/ doesn't work on Windows for ARM64 (stuck at 99%) #1414

Open
kkoreilly opened this issue Jan 3, 2025 Discussed in #1413 · 5 comments
Assignees
Labels
bug Something isn't working correctly confirmed This bug has been confirmed high priority This issue should be resolved quickly
Milestone

Comments

@kkoreilly
Copy link
Member

Discussed in #1413

Originally posted by SideFx January 2, 2025
Used Chrome & Edge as browser. Progress bar stucks at 99%.
Any ideas?
Thank you.

@kkoreilly kkoreilly added the bug Something isn't working correctly label Jan 3, 2025
@kkoreilly kkoreilly added this to the v0.4 milestone Jan 3, 2025
@kkoreilly kkoreilly self-assigned this Jan 3, 2025
@github-project-automation github-project-automation bot moved this to Todo in Bugs Jan 3, 2025
@kkoreilly
Copy link
Member Author

@SideFx Thank you for reporting this. Please open the Chrome developer tools / inspector / console and copy any error message you see in the console here (there should probably be a panic and a stack trace). Please also go to chrome://gpu, click Download Report to File, and then upload the resulting file here. Thank you!

@SideFx
Copy link

SideFx commented Jan 3, 2025

Thanks for the quick response, I did as suggested, here's the error log:
core wasm mesg.txt

@SideFx
Copy link

SideFx commented Jan 3, 2025

And here's the GPU log:
about-gpu-2025-01-03T22-45-15-903Z.txt

@kkoreilly
Copy link
Member Author

kkoreilly commented Jan 4, 2025

@SideFx Thank you for providing that debug information. The GPU device report states that WebGPU is not supported on Windows arm devices, so the solution to this is to correctly use the backup 2D drawer when WebGPU isn't supported but is declared as such (browsers provide a navigator.gpu field even when they don't support WebGPU in cases like this, so we need a more advanced fallback procedure). We have been meaning to do this before and it shouldn't be too hard to implement. This should also fix issues with other browsers such as Firefox Nightly, Brave, Kiwi Browser, and Linux browsers, as we can now have a robust WebGPU enabling rule instead of a limited heuristic. We will fix this as soon as possible. See also the more long-term #1144.

@kkoreilly kkoreilly added confirmed This bug has been confirmed high priority This issue should be resolved quickly labels Jan 4, 2025
@SideFx
Copy link

SideFx commented Jan 4, 2025

Thank you very much. If I could be of any assistance pls let me know.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working correctly confirmed This bug has been confirmed high priority This issue should be resolved quickly
Projects
Status: Todo
Development

No branches or pull requests

2 participants