It's very unlikely. Of all sites, this one consumes only what's needed for server-rendered pages with minimal client-side JavaScript. Each page is created and destroyed anew, so there's really no room for a memory leak.
The cause must lie elsewhere: the browser, your network connection, whatever other apps you've got running, etc.
1 comment
[ 2.2 ms ] story [ 24.0 ms ] threadThe cause must lie elsewhere: the browser, your network connection, whatever other apps you've got running, etc.