Currently, if you leave the MicroLab running for days, you get a ERR_INSUFFICIENT_RESOURCES error when making network requests. This likely indicates a memory leak that wants to get tracked down.
As a short-term fix, the network request util functions can include a try / catch (possibly just the status request as it is something that runs regularly) such that when the ERR_INSUFFICIENT_RESOURCES error is caught, it reloads the UI by refreshing the window. This would be jarring if a user saw it, but should not have an impact on the MicroLab's function. It would also be good to log the error for further investigation.
For Release v0.6.0 we've done some performance tuning and eliminated two likely causes of this. Closing for now until we confirm it is still happening.
Currently, if you leave the MicroLab running for days, you get a ERR_INSUFFICIENT_RESOURCES error when making network requests. This likely indicates a memory leak that wants to get tracked down.
As a short-term fix, the network request util functions can include a try / catch (possibly just the status request as it is something that runs regularly) such that when the ERR_INSUFFICIENT_RESOURCES error is caught, it reloads the UI by refreshing the window. This would be jarring if a user saw it, but should not have an impact on the MicroLab's function. It would also be good to log the error for further investigation.