It creates new canvas once state is changed about react HOT 2 OPEN

This was my problem too. I ended up not using states cause it also clears the mouse event handlers on my matterjs side as the canvas gets re-rendered. I tried to use React.memo on the wrapper but I got more bad side effects. I suggest using just refs to store values and put your sketch function inside the component where the wrapper is so that it has access to the refs:

export default function App() {
  const measurements = useRef([
    {
      id: 1,
      ref: {
        x: 100,
        y: 100,
      },
    },
    {
      id: 2,
      ref: {
        x: 200,
        y: 100,
      },
    },
  ]);

  const sketch = (p5) => {
    p5.setup = () => {
      // loop thru measurements.current 
      // and create your Measurement objects
    }
  };

  return (
    <div className="App">
      <ReactP5Wrapper sketch={sketch} />
    </div>
  )
}

from react.

I think this is more to do with the fact you are trying to use p5 as if it is in global mode, i.e you are assuming that the variables and methods will exist or do the cleanup for you. In this case, the error is clear when it says WARNING: Too many active WebGL contexts. Oldest context will be lost.. This error is triggered by p5 itself when you create more WebGL instances than is required. This library will properly destroy a p5 instance but p5 itself will only clean up if certain pre-requisites are met, but in your case, there seems to be some dangling reference to a WebGL context on each cycle which is then never released and thus "too many" exist after some time.

I also don't believe that moving the variables into a ref is the answer either, in this case you actually have constant data and from what I can see, the OP never calls the setter function (which is also bad practice in React to pass around). In such as case I would just have a const in the top level, like:

type Props = { ... }

const measurements = {...};
const sketch: Sketch<T> = p5 => {...}

export function App(props: Props) { ... }

In the Measurement class you don't need initVariables either since updateWithProps is called on every render and will get all props on initial render also too.

Just some tips.

from react.