Comment by foxglacier

"reveals", not "causes". The memory leak, if it truly exists, was already present. It's not a website's fault for triggering it.