Issue with Selective Outlines in new versions of packages

[JTatum95]

I've been running into an issue with Selective Outlines since updating React, Fiber, DREI, and Post-Processing to their latest compatible versions. Now whenever the Selection is active it fills the console with errors saying "Maximum update depth exceeded. This can happen when a component calls setState inside useEffect, but useEffect either doesn't have a dependency array, or one of the dependencies changes on every render."

See this example using a modified version of the Post Processing Selective Outlines Example project - https://codesandbox.io/p/sandbox/selective-outlines-forked-68r9ql

Here is the example unedited - https://codesandbox.io/p/sandbox/d36mw

Is there a way to get around this? An expected fix on the horizon? Or any guidance in how I can find a compatible version of all these that I can install that won't hit this issue.

From what I can tell the outlines work as expected so I'm not sure how concerned I should be but I don't want to ship a project with this error popping up.

[travisbreaks]

Known issue from a version mismatch between @react-three/postprocessing and the R3F reconciler.

The Selection component uses a context provider that triggers re-renders when the selection set changes. In newer React 18.x + R3F versions, the useFrame loop and the selection context can create a circular update: the outline effect reads the selection, which triggers a re-render, which updates the selection reference, which triggers another render.

Stabilize the selection reference by memoizing it. Wrap your selection set in useMemo so the reference only changes when the actual selection changes, not on every render. If that doesn't fix it, check that @react-three/postprocessing and @react-three/fiber are on compatible versions; the postprocessing package often lags behind R3F releases and the internal APIs drift.

[bubblyeducate]

Looks like a render loop from unstable dependencies with React 18. Try memoizing props passed to Selection/Outline and disable StrictMode to confirm. Otherwise, lock to a known working version combo — bitlife likely a compatibility issue with the latest updates.