1 hour ago · Tech · hide

You’re welcome to all developers that user Render.com. I recently discovered that their interactive shells in the dashboard had a memory leak. Memory would not be returned to your service if a shell crashed in your browser. And those shells did not play well with ad blockers like uBlock Origin. As such I’ve found Render in-browser shells could crash quite often. For several years we noticed that server memory grew over time in ways we could never explain, even with a lot of troubleshooting. Sometimes the leak would saturate all of our server’s memory. A server restart would clear things out, so eventually we even had background jobs set up to restart our servers a few times a day to “fix” the memory leak. Last week I finally sat down and dug a little deeper when a lesser-used server started crashing right as I was taking a rare chance to work on it. Processes galore! I’m told this has now been fixed up. Perhaps now I can reduce some of our serve allocation… Reply by email

Commenting on Bubbles has been removed. Why? If you want to talk about this post, write to the author, use the comments on their blog if it has them, or reply with a "RE:" post on your own blog. Suggestions? feedback@bubbles.town