-
Notifications
You must be signed in to change notification settings - Fork 42
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Additional tabs can no longer connect after 10 open tabs in browser #752
Comments
hey @dmh1974, unable to access the above IPFS CID - can you please confirm if this is still a bug on your end? |
This is a bug report. Let's try to reproduce ourselves first before icing/discarding. |
For now, let's just investigate:
If the bug still exists then web workers maybe a solution. |
Issue is not observed on 11+ tabs. I think it's safe to close though idea with a web worker is useful and I propose to pursue it in this issue waku-org/examples.waku.org#211 I had strange behaviour at https://examples.waku.org/relay-js/ when connection to the node fails. Is it happens to you too @danisharora099 / @fryorcraken ? |
Yes, waku-org/pm#23 |
currently using testnet
maybe nwaku related
you can reproduce the results here
https://gateway.pinata.cloud/ipfs/QmUS84DM9wLhmXnVf1EB41uoGc4HobTPc9W2CMAUWQRMFs?topic=BTCUSDT
duplicate tabs, 11th+ tab and so on will not connect
The text was updated successfully, but these errors were encountered: