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 recently started encountering errors while syncing users on certain devices. This error sometimes leads to an inability to initialize zk the account and therefore to use our application.
After some local debugging I realized that the main issue is TimeoutError in IndexedDB.
I am not entirely sure but I think what happens in our case is something like this:
It should be noted that the current implementation of IndexedDB wrapper doesn't wait for transaction to commit, so it just creates some pending txs that eventually should be automatically committed
So, if we have pending database transactions and start parsing zeropool transactions, the Web Worker thread remains constantly busy, and as a result, the autocommit fails to complete within 60 seconds.
Finally, we have some timeout error that leads to panic in wasm and aborting state sync
We recently started encountering errors while syncing users on certain devices. This error sometimes leads to an inability to initialize zk the account and therefore to use our application.
After some local debugging I realized that the main issue is TimeoutError in IndexedDB.
![image](https://private-user-images.githubusercontent.com/17165678/258055297-8a7bdeff-1c19-45c8-9a7e-65f112f21f5a.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MjIxMTQxNzEsIm5iZiI6MTcyMjExMzg3MSwicGF0aCI6Ii8xNzE2NTY3OC8yNTgwNTUyOTctOGE3YmRlZmYtMWMxOS00NWM4LTlhN2UtNjVmMTEyZjIxZjVhLnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNDA3MjclMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjQwNzI3VDIwNTc1MVomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPWU3OTkxNDQyNzI3MWNmYmNiNzRhODliYWZkY2EwZTFkOTUwODMyZmY5YzNhZmMwYzViOWRlMTNmM2U3YjA3ZGEmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0JmFjdG9yX2lkPTAma2V5X2lkPTAmcmVwb19pZD0wIn0.DJllTHE_9L5xU4_61kd3wnq9Tg_NLmg1OHJk3lD6rT8)
I am not entirely sure but I think what happens in our case is something like this:
Refs:
PR: #69
The text was updated successfully, but these errors were encountered: