Can you provide a reproducer for the error? Is this related to #1936?

urlSyncEffect() is used the same as syncEffect() with just the addition of the history option. See these examples

I have the same issue.
I tried to reproduce it in this codesandbox: https://codesandbox.io/s/stupefied-tree-c2xd7t?file=/src/component.js. The error is thrown when you change the array size (for example from 500 to 5000:

)
I tested this code on Chrome and it doesn't throw any error but it does in Firefox (104.0.2 & 105.0b9). I only tested those 2 browsers.
Also, I don't know if it's the same cause as in my full code.

@PiR1 try using the 7.6 release as this resolved the issue for us, we was on 7.4.

@PiR1 try using the 7.6 release as this resolved the issue for us, we was on 7.4.

Yes, I'm on the latest version in my code and in the codesandbox but it doesn't resolve the issue.
As I said in the issue #1936 (which has been "resolved" in the version 7.5), the timeout delay added depends of the computer and app performances. So it doesn't fix the issue in all cases.

I have this issue as well using recoil 0.7.6 and recoil-sync 0.2.0.

I'm tied to a very specific version of webkit/safari webview and this issue makes it virtually impossible to use recoil-sync at all since the dev tools can not be opened without crashing the app

I'm having this issue on recoil 0.7.7, but only when using react 18.2.0, if I use react 17.0.2 the issue does not occur.

For reference, I am encountering this using a custom component in storybook, and it only occurs under specific circumstances

I see #2243 is already merged. When are we going to release a new version with this fixed? Thanks!

Hi, what is the status here? I see there is a PR #2243 (not merged) but no movement in a while...

I will close off this issue for now. It's been a while and I've mostly relied on chrome to avoid the hassle.
For those who are experiencing the same issue, I'd suggest using the chrome browser especially for handling large set of data which seems to be the case.

how resolve the problem ?

@Jeffy-Praneat I added pnpm patch to the autoRelease_INTERNAL() function, making the timeout 100ms rather than 10, and now it works, see this issue - #1936

@chriszrc Thanks, it did the trick for my app