Chrome 83: Feedback loop formed between Framebuffer and active Texture

[bipy]

Google Chrome 83.0.4103.61 x64

When loading the demo page ( others as well ):

just show like above for one or two second, and then go dark.
Mouse Click cannot light it then.

Console info:

[.WebGL-00000278FED10820] GL_INVALID_OPERATION: Feedback loop formed between Framebuffer and active Texture.
* 256 times
WebGL: too many errors, no more errors will be reported to the console for this context.

• It has worked perfectly until today.
• Another computer ( call it PC1 ) can run normally ( Chrome 81 )
• When PC1's Chrome update to 83, same problem occurred.

So I guess the problem is Chrome's new version.

[bipy]

#41
Maybe same reason

[matthew-kaye]

Interestingly, websites like https://cauldron.co/?fbclid=IwAR04lkI-C6VEnXtiEuZslzFOLg7GBNu3LzhtoDbzxjI-thLliIhT58jgLYc have seen their animations change, and get the same error message, but without the same kind of pixellation. Their script is here: https://cauldron.co/assets/themes/cauldron/js/fluid.js

[ENiGMA9]

Any idea for a fix? :(

[chuzzbot]

You know the error only occurs with gpu acceleration on?
Switch it off and Fluid sim works as expected ( albeit much slower).
Does that give any clues to a solution?

[matthew-kaye]

Appears to be Windows-specific, fine on Mac Chrome update

[PavelDoGreat]

wow wtf gonna look into this issue but I don't have a pc where I can replicate it

[PavelDoGreat]

Any developer here that experience same problem? Can you try to figure out which parts of simulation causes this by commenting out code stages like Vorticity, Pressure and etc.

[matthew-kaye]

I'd only got as far as working out that in the update function it renders the null frame fine but starts having issues when "requestAnimationFrame(update)" is called, which I guess isn't saying much more than that it errors when it renders

[matthew-kaye]

Chatted to some Google people about it (https://bugs.chromium.org/p/chromium/issues/detail?id=1087683#c2) - interesting to note that it works fine in Chrome Canary on Windows too

[matthew-kaye]

TL;DR I think it's fixed in Chrome v84, might not actually need a code change

[PavelDoGreat]

epic

[matthew-kaye]

Think we can close this now! A tiny update to 83.0.4103.97 for standard Chrome means it all seems to work, happy fluids all