Memory leak with lots of on screen log updates

[mainmachine]

I'm running docker-dnsmasq and it works great, however if I keep a tab open it will quickly begin to eat up all of my RAM.

Dnsmasq works perfectly, so it appears this is only an issue with webproc.

Here's my initial report of this issue against docker-dnsmasq.

Only clue at this point is lots of entries for run.js:55 in the browser console:

[mainmachine]

Comcast has been down for a bit today, and that triggered an interesting phenomena, which has led me to conclude that this issue is caused by bad configuration, and not a memory leak.

We had our DHCP server specified as a third DNS server in our dnsmasq config, but the DHCP server is also pointing to the dnsmasq container itself as the primary DNS server. When our ISP went down today, the only reachable server in our dnsmasq conatiner's list was the DHCP server, which created a loop as each one forwarded the request back to the other, ad infinitum...

Removed the DHCP server from the dnsmasq container's list and now the logs have calmed down.

TIL how to create a DNS forwarding loop. :D