RAM usage Skyrocket

[Bonnary]

I try messing around with react-three-fiber code and it works fine but when I tried using it in my project it gives out an " InternalError: too much recursion " or the browser try its best to run it and then the RAM usage goes to maximum and crashed my computer.

[joshuaellis]

You've used the useLoader hook incorrectly. You don't need to pass it an imported image you pass it a url.

[Bonnary]

You've used the useLoader hook incorrectly. You don't need to pass it an imported image you pass it a url.

Do you mean like this?

const texture = useLoader(
THREE.TextureLoader,
"../assets/3D-texture/moon.jpg"
);

but isn't this the same thing? I read the document 5 times now and still don't understand it.
In the document they use import { TextureLoader } from "three/src/loaders/TextureLoader"; I already did like what they did and still get the same result.

[CodyJasonBennett]

The imported image gets converted to an absolute URL by react-scripts -- the usage is fine, although earlier versions convert it to an ES module.

As for the behavior here, does this issue persist on r133 or earlier?

[drcmda]

making this a discussion for now. probably similar to #1806 in general loaders are something that has to do with threejs itself, these things are usually not related to r3f, it just calls the loader.