Why can't the memory be released even when there is no request?

Hello, i have a few problems about splash. I wish i could get some help.

• It seems that about 1000 urls will cost more than 1GB memory, which cannot be released.
• The doc says the /_gc endpoint will run garbage collection. But in my trial, it doesn’t free the webkit memory.
• After we set the --restart=always, once the splash shuts down and restarts, the requests coming in during that period all fail to get the content.

[PornthipSaechong]

I had this issue too. I found a work around by calling /execute rather than /render.html and pass custom lua script to close the rendered window. I believe render.html only load webpage and not closing it. This leads to memory leak. By forcing the window to close every time, it frees up the memory taken up. I did this and docker memory became very stable.

Here is the lua script I use:

function main(splash) local url = splash.args.url assert(splash:go(url)) assert(splash:wait(0.5)) local html = splash:html() splash:runjs(“window.close()”) return html end

Hope this helps 😃

[kmike]

_gc calls everything I could find in qt API to clear caches, but it looks like sometimes this is not enough. If you want to handle restarts gracefully the way to go is to setup a load balancer (e.g. haproxy) which re-schedules requests to other instances if they are dropped. See e.g. an example config template here (it is not a config itself, it is a cookiecutter template).