I’ve recently changed all my monitors to load pages in background instead of in tab. What happens now is the Distill extension slowly increases its memory footprint until it crashes/gets shut down by the browser. The leak increases gradually with every monitor check.
Stopping the monitors prevents further leak, but does not release the memory. Only disabling the extension or closing the browser does.
Tested both in Opera and Chrome, in the latter case after settings reset and deleting any other extensions to make sure there’s no third party involved.
Hello @lee6pl, thanks you for reporting this issue. This is very helpful. IIRC another user faced a similar issue. But we were unable to reproduce this issue in our development environment.
When using background checks, Distill loads the pages in the background to parse and filter data. It is possible that in some cases there is a memory leak. A few questions:
What is the average check interval for the monitors?
Are they all from the same website or from different ones?
Using Chrome 116.0.5845.188 with Windows 11, Distill Web Monitor crashes several times a day. It has crashed like this for the last month at least. I have 11 monitors setup to scan every 15 seconds to 5 minutes, some with Javascript disabled. I’ve tried disabling all other Chrome extensions, but the frequent crashing still occurs. Any suggestions?
The most likely cause is static checks for a certain website in a specific Chrome version. One of the challenges for our team has been inability to reiably reproduce the crashes. That is because these crashes are triggered by combination of multiple factors. Can you try to narrow it down to a specific monitor by turning off a subset of monitors and only keeping a few on? Thanks!
