Cpu times increasing over time indefinely when using postprocessing

[Agusmac]

Hi again

Ive been using postprocessing over my whole site (just a landing page) and discovered that when global render is set to false (to use the effect)
the Cpu times increase over time, to the extent that in a couple of minutes, my site cpu times go from 0.5ms to 26ms
I tested some things and figured some things

the more elements rendered to the canvas, the faster this increase goes and some increase it more than other
-geometries: low/no impact (maybe if you add 10K cubes it might but not with a normal amount)
-Text: higher impact
-Images(textured planes): much higher impact

i checked all of this with R3f-Perf
and no other values(calls/polys) seemed to change
and no increase in gpu memory use

Noticed when using my custom postprocessing, but also happens with bloom and other defaults

Here is a sandbox with the issue, using the postprocessing sandbox from the docs:
https://codesandbox.io/p/sandbox/hello-post-processing-forked-wzdd5m?file=%2Fsrc%2FText.jsx%3A34%2C15
If needed i can provide other heavier examples that may show the issue faster (low loads may take 5-10 mins, but the site im building needs 2 to start dropping frames)

Any workarounds are welcome!
Thanks!

[ffdead]

Hi @Agusmac - interesting, I had not noticed that.

Have you made any tests with the same versions of all the libraries and dependencies but without the scroll-rig to see if it still happens?

[ffdead]

Update: left the sandbox open for over an hous and still show 120fps on my Macbook M1 Max

[Agusmac]

Hey @ffdead
I had a version with postprocessing that worked fine before (only had the hero scene), after that i added scroll-rig and did the rest of the page
Tried several versions of packages and nothing changed, but given i tried with several of my projects i think the issue may be in the scrollrig

Some notes
-turning global render on again fixes it, but => disables effect composer
-im on Windows+ i5 12400 + 3070, the issue is in chrome and id say maybe a bit worse in Firefox
-quite sure moving the mouse- scrolling may accelerate the issue
-u must be on the tab, the issue may present without it but its much noticeable this way
-the issue acelerates the most if the plane images are on view

This is a WIP so i probably will delete this after, but if it doesnt drop your frames, or at least scalates cpu times a lot in chrome,
maybe the issue is how windows or even the cpu handles things
https://agusmac-portfolio.vercel.app/