Practical JS: getting rid of memory leaks in IE
Note: Below is a translation of the article Understanding and Internet Explorer Leak Patterns , in which the author examines some typical cases of memory leaks in IE and suggests methods for avoiding and eliminating them. The problems discussed are not new or revolutionary, but know about their existence must any self-respecting client programmer My comments further in italics.
Published: June 2005
')
In the past, memory leaks did not create any problems for web developers. Pages were extremely simple, and the transition from one to another was the only normal way to free up all available memory. If a leak occurred, it was so insignificant that it went unnoticed.
Modern web applications should be designed to meet higher standards. The page can run for hours without additional navigation through the site, while it will dynamically request new information itself via web services. The language engine is tested for durability by complex event processing schemes, object-oriented JScript and closures , producing ever more powerful and advanced applications. At the same time, taking into account some other features, knowledge of the characteristic patterns of memory leaks becomes more and more necessary, even if they were previously hidden behind the site navigation mechanism.
A big plus in this situation is that memory leak patterns can be easily detected if you know where to look for them. The most difficult of them that you may have come across are described in detail with the elimination methods, which, most likely, in your case will require only a small amount of additional work. While some pages may still fall due to small leaks, the most significant ones can easily be removed.
read further on webo.in →
Published: June 2005
Web development
')
In the past, memory leaks did not create any problems for web developers. Pages were extremely simple, and the transition from one to another was the only normal way to free up all available memory. If a leak occurred, it was so insignificant that it went unnoticed.
Modern web applications should be designed to meet higher standards. The page can run for hours without additional navigation through the site, while it will dynamically request new information itself via web services. The language engine is tested for durability by complex event processing schemes, object-oriented JScript and closures , producing ever more powerful and advanced applications. At the same time, taking into account some other features, knowledge of the characteristic patterns of memory leaks becomes more and more necessary, even if they were previously hidden behind the site navigation mechanism.
A big plus in this situation is that memory leak patterns can be easily detected if you know where to look for them. The most difficult of them that you may have come across are described in detail with the elimination methods, which, most likely, in your case will require only a small amount of additional work. While some pages may still fall due to small leaks, the most significant ones can easily be removed.
read further on webo.in →
Source: https://habr.com/ru/post/31437/
All Articles