Continuously changing the Chrome browser window size can cause memory leakage

Recently, in a responsive layout page, in the development and testing process, in order to see the performance of the page in windows of different sizes, we need to drag the browser to change the window size; I started to view the page in the Chrome browser and dragged it several times. I felt that the computer was obviously stuck, but I didn't care about it. Then I opened the Task Manager and checked it, when the browser window size is constantly changed, the memory usage will suddenly increase and the browser window will not be closed, and the occupied memory will not be released. Later I tested it in several other browsers and found that operabrowser also had this phenomenon. In order to compare it, I changed the memory of the Task Manager and marked it, for example:

 

According to the changes in the image, we can see that when Safari and Firefox change the window size, there is no memory leakage, chrome and Opera will only release the memory occupied by this part after closing the browser window.

According to my estimation, the size of the browser may change, resulting in page re-arrangement. During this process, memory leakage occurs in the browser rendering kernel. Of course, this is just my guess based on the above situation and there is no evidence, so I will share this situation to see if anyone has ever encountered it and whether there is any informed reason.

 

 

Test the browser version:

Chrome: 38.0.2125.111 m

Opera: 25.0.1614.68

Safari: 5.1.7 (7534.57.2)

Firefox: 1, 30.0

 

  

Continuously changing the Chrome browser window size can cause memory leakage