Open arpee opened 3 weeks ago
Browser at rest and fully synced begins loading historical blocks 'for no apparent reason'.
I have attached a file to 20 mins or s of console log most of which is this kind of output:
fetching block from url : https://saito.io:443/lite-block/0274a50024f37e42d866e850243ee6f6fba8bd264d0c8a91c83f1786b3a9a6bf/i767FqhGcKPzqi7KcWNA8TQoTZeBd8QbWd2mTKNnkfmk block fetched from : https://saito.io:443/lite-block/0274a50024f37e42d866e850243ee6f6fba8bd264d0c8a91c83f1786b3a9a6bf/i767FqhGcKPzqi7KcWNA8TQoTZeBd8QbWd2mTKNnkfmkwith size : 7775 fetching block from url : https://saito.io:443/lite-block/16ea7d459b6b14ea30c6e2f284cd7a40d1bcc50249b49b7f0fe534e487f920b6/i767FqhGcKPzqi7KcWNA8TQoTZeBd8QbWd2mTKNnkfmk block fetched from : https://saito.io:443/lite-block/16ea7d459b6b14ea30c6e2f284cd7a40d1bcc50249b49b7f0fe534e487f920b6/i767FqhGcKPzqi7KcWNA8TQoTZeBd8QbWd2mTKNnkfmkwith size : 1649 fetching block from url : https://saito.io:443/lite-block/0e2bcde85da457e6db5b680e2cec6ce2c8b24c497dabfcec33c3be9ff6dae9c5/i767FqhGcKPzqi7KcWNA8TQoTZeBd8QbWd2mTKNnkfmk block fetched from : https://saito.io:443/lite-block/0e2bcde85da457e6db5b680e2cec6ce2c8b24c497dabfcec33c3be9ff6dae9c5/i767FqhGcKPzqi7KcWNA8TQoTZeBd8QbWd2mTKNnkfmkwith size : 2115 fetching block from url : https://saito.io:443/lite-block/9fb63ae85da4d65d66cbfabaa5f7ea550f3e628adcf79489d691cf2ce7dfae9b/i767FqhGcKPzqi7KcWNA8TQoTZeBd8QbWd2mTKNnkfmk block fetched from : https://saito.io:443/lite-block/9fb63ae85da4d65d66cbfabaa5f7ea550f3e628adcf79489d691cf2ce7dfae9b/i767FqhGcKPzqi7KcWNA8TQoTZeBd8QbWd2mTKNnkfmkwith size : 245 Automatically checking for new content on RS...
This happens whenever my browser is idle. The blocks being requested existing on disk at the node but should already be known to the browser.
console_logs.txt
Note - I checked the out put and some rows are repeated... i have attached a list.
repeated.lines.txt
Browser at rest and fully synced begins loading historical blocks 'for no apparent reason'.
I have attached a file to 20 mins or s of console log most of which is this kind of output:
This happens whenever my browser is idle. The blocks being requested existing on disk at the node but should already be known to the browser.