You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We are facing an issue on random devices on specific browsers that can be related to the safe-json package.
Basically, it keeps trying to set them on the storage but it fails(maybe) and keeps trying till it runs out of memory
This only happened after upgrading to the latest web3modal v2, and it still happens on v3.
Steps to reproduce?
It happens for random users so we don't know what the problem is, it happens locally for some dev members and doesn't happen on production for the same devs with the same config (browser).
hey @Mostafatalaat770, do you have any steps to reproduce it?
The storage, while persistent, keeps data in memory during its lifecycle and reads from file/storage when its launched.
This means that if your implementation has some circular/looping setItem calls, the memory would increasing with that.
For example this might happen if you're creating new pairings all the time for some reason or similar.
We had previous reports where react components were repainted constantly causing similar issue
I would check first if that is the case
We are facing an issue on random devices on specific browsers that can be related to the
safe-json
package.Basically, it keeps trying to set them on the storage but it fails(maybe) and keeps trying till it runs out of memory
This only happened after upgrading to the latest web3modal v2, and it still happens on v3.
Steps to reproduce?
It happens for random users so we don't know what the problem is, it happens locally for some dev members and doesn't happen on production for the same devs with the same config (browser).
Versions
Working:
"@walletconnect/modal": "^2.5.7",
"@web3modal/ethereum": "2.6.0",
"viem": "1.0.7",
"wagmi": "1.3.3"
Problematic:
V2:
"@web3modal/ethereum": "2.7.1",
"viem": "1.19.6",
"wagmi": "1.4.7"
V3:
"@web3modal/wagmi": "^3.3.2",
"viem": "1.19.6",
"wagmi": "1.4.7"
The text was updated successfully, but these errors were encountered: