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

Potentially uninitialized variable #672

Open
Wizer21 opened this issue Aug 23, 2024 · 3 comments
Open

Potentially uninitialized variable #672

Wizer21 opened this issue Aug 23, 2024 · 3 comments

Comments

@Wizer21
Copy link

Wizer21 commented Aug 23, 2024

Hello !

I have a warning saying that a variable is not initialized in the shader, when it appears, the browser freezes for 10-30s.
I've tried several examples from the library, this doesn't seem to be the issue.

The issue seem's to be similar to the post #325

It sometimes appears on chrome and edge.
But for my computer i always have it on firefox, no matter the version.
I also had it on other computers.
mozz_105 0

Graphic card NVIDIA GeForce RTX 3070 Ti Laptop GPU
Processor 12th Gen Intel(R) Core(TM) i9-12900H 2.50 GHz
Chrome 128.0.6613.85
Edge 127.0.2651.105
Firefox 129.0.2 ( also tried 128/125/115/105 // v105 was published the 18-Mar-2023 )

@Wizer21 Wizer21 added the bug Something isn't working label Aug 23, 2024
@gkjohnson gkjohnson added browser / device issue and removed bug Something isn't working labels Aug 23, 2024
@gkjohnson
Copy link
Owner

It was definitely working in previous version so if previous versions aren't working on Windows now then there's been a new regression or change with without any useful logs. Can you check this examle and this example? Otherwise tracking these kinds of errors down is a nightmare.

the browser freezes for 10-30s.

Unfortunately this is a known Windows issue we have no control over due to the shared compiler being used used under the hood. See #325 (comment).

@Wizer21
Copy link
Author

Wizer21 commented Aug 23, 2024

The first time I opened them, I had this problem. But it never happened again, even when I restarted the computer, cleared the cache or used private browsing.

error2 1
error1

@gkjohnson
Copy link
Owner

Looking through those functions in three-mesh-bvh briefly I don't see anything that sticks out as an issue. The first step would be figuring out how to repro the warning consistently so we can make sure it's been fixed. Changing the shader string slightly may force a recompilation even if clearing cache isn't removing the shader for whatever reason so we can see the error reliably.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants