BTW, there is a major fail in one of the javascipt objects that is screwing my browser over. The page suddenly froze the entire browser, so I went to look at the memory usage and it was at --4GB-- yes 4 gigabytes. I was able to kill the offending script after waiting a bit and letting it time out, and the memory usage immediately dropped to 550MB.
The same thing has been happening to me. I'm pretty sure it has to do with the speed box on the worker page. If it's set to live the memory jumps up quick until the browser crashes, but if I switch it to 24H then everything works fine.
Well for me, once I killed the script and then refreshed the page, it started working again fine. However, when it froze up, I was on the edit page looking at the worker PPS rate, not the stats page with the speed.
One thing I noticed was that when I tried to change the PPS rate, it kept reverting back live, as if there was a socket.io connection pulling in the current price. But that didn't work as expected, because all it did was revert back to what I had set, instead of reverting to a given price. I assume that the same bit of javascript is used on both pages for socket connections, and that may be why the random memory leaks are happening on both pages.