Interesting use case. You should unmount the component when closing the window (unrelated to data grid):
https://codesandbox.io/p/sandbox/fervent-bessie-rn3h8m?file=%2Fsrc%2Fuse-open-window.tsx

You can also delay rendering to avoid the remaining errors, as a new popup has no dimensions initially. But that's not really an issue.

Sorry I got the wrong version of React in the codesanbox, with react version 18 the error still appears. My temporary solution is to go back to version ‘@mui/x-data-grid-premium’: ‘7.22.3’, and update the create window hook.

As for delaying the rendering, it could also be a valid solution, but it seemed to work in the previous version of the library, so I guess it is a bug with the new react 19 changes.

Whats interesting and weird: If you add a second function call to the unmount it does work. Noticed because I wanted to log something to the console, so that alone is enough to make the error disappear. Not sure why that is though. This couldn't be because the log is pushed onto the stack, no?

Sorry I got the wrong version of React in the codesanbox, with react version 18 the error still appears. My temporary solution is to go back to version ‘@mui/x-data-grid-premium’: ‘7.22.3’, and update the create window hook.

Which error? Can you provide a reproduction?

Update draft with react and react dom version 18.

Click in open window
Close the new window
Inspect in the console
Infinite loop error

https://codesandbox.io/p/sandbox/stoic-bassi-f4fckg

Update draft with react and react dom version 18.

Click in open window Close the new window Inspect in the console Infinite loop error

https://codesandbox.io/p/sandbox/stoic-bassi-f4fckg

I cannot seem to reproduce the infinite loop error. I only see a The parent DOM element of the Data Grid has an empty width. error (which is more a warning than an error).

I could reproduce it with React 18, so the issue is indeed present, but as stated it goes away with a second function being called before the root.unmount call

I guess wrapping in a setTimeout( ... , 0) would work as well. Could you check that @danciudev ?

The above PR should fix it. The problem might be particular to dev mode though, as it happens intermittently, but still.

You still need to call unmount though, as otherwise you're continuing to render the component even after the popup window closes, as the rendering is handled by the parent window – stripped down example / reproduction without any data grid:
https://codesandbox.io/p/sandbox/polished-sun-lcyy8r

Perfect, thanks

This issue has been closed. If you have a similar problem but not exactly the same, please open a new issue.
Now, if you have additional information related to this issue or things that could help future readers, feel free to leave a comment.