In some cases the navigation cannot be performed immediately, e.g. slow network connection, waiting for IPFS to resolve. As a result, tab.url will be empty and the URL to be navigated is in tab.pendingUrl. See the docs.
In such cases, this extension will try to check tab.url infinitely without any delay, leading to high CPU usage (around 100%) and computer fan noise.
The fix is to check pendingUrl as well as url, and if that fails too, add a delay before the next check.
In some cases the navigation cannot be performed immediately, e.g. slow network connection, waiting for IPFS to resolve. As a result,
tab.url
will be empty and the URL to be navigated is intab.pendingUrl
. See the docs.In such cases, this extension will try to check
tab.url
infinitely without any delay, leading to high CPU usage (around 100%) and computer fan noise.The fix is to check
pendingUrl
as well asurl
, and if that fails too, add a delay before the next check.