About JavaScript memory leaks. Again.

Worth to read, at least, if you are not JS dev

Anton Gorbikov's avatarAnton Gorbikov's Blog

Web applications are getting more and more complex from year to year. Couple of years ago nobody cared about the memory leaks on the web pages (yeah, they were really a set of web pages, but not web applications). Even if you forget to clean up some memory – it’s not expected, that user will spend a lot of time on the same page. There were a lot of navigation links, which removed information about the entire page from memory and loaded new page.

But now you cannot relate on this behavior, because now web sites turned into web applications. User loads one small HTML file, one script file and some other stuff (like CSS and images) and that’s it. Making requests from browser to servers user can stay on on the “page” for ages. In the worst scenario you will receive a report from production user: “Oh, your application…

View original post 2,020 more words


Discover more from Sergey Tihon's Blog

Subscribe to get the latest posts sent to your email.

One thought on “About JavaScript memory leaks. Again.

Leave a comment