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

code suddently broke #787

Open
florentmaye opened this issue Nov 2, 2022 · 3 comments
Open

code suddently broke #787

florentmaye opened this issue Nov 2, 2022 · 3 comments

Comments

@florentmaye
Copy link

What is wrong?

I have created a CAD software based on gpu.js. It was working fine last few weeks. But suddently I'm getting errors like:

Uncaught Error: Error compiling fragment shader: ERROR: 0:584: 'normalize' : Name of a built-in function cannot be redeclared as function ERROR: 0:597: 'dot' : Name of a built-in function cannot be redeclared as function

What bother me is that I made no change to my code,. I'm using:

<script src="https://cdn.jsdelivr.net/npm/gpu.js@latest/dist/gpu-browser.min.js"></script>

So I was suspecting a new version broke it, but that doesn't seem to be the case (no new version) and forcing an older one doesn't change anything.

Of course I tried renaming the function causing this issue, but it creates other errors. At this state I'm not able to correct them as GPU.js error are opaque (CPU mode doesn't work anymore in my case), and I already have thousand lines of working code that make hard to investigate them.

How do we replicate the issue?

maybe try to create a function named 'dot', previously it wasn't creating an issue, but now it does

How important is this (1-5)?

5: my CAD software I spent a lot of time developping and I'm using for my business doesn't work anymore :'(

Expected behavior (i.e. solution)

If not coming directly from GPU.js (what I suspect), maybe a webgl API update broke everything? I try to force webgl1 context, but unsuccessfully. Any clue on how I could patch this?

Other Comments

Thank you for this great tool

@florentmaye
Copy link
Author

Weirdly, on other computers (with same browser up to date), this issue has not appeared.... I'm having a hard time identifying its cause

@pmartin-cogility
Copy link

I just started seeing this also. There's not much out there on Google about this error.

@amacciola
Copy link

Seems something between Google Chrome version 106.0.5249.119 -> 107.0.5304.87 current. Cause this issue to start popping up

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

No branches or pull requests

3 participants