search

shailesh17 / chrome-reload

Automatically exported from code.google.com/p/chrome-reload
0 stars 0 forks source link

memory leak #15

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
What steps will reproduce the problem?
1. open Chrome task manager
2. open new tab in Chrome
3. browse to http://www.google.com/
4. set 5 second refresh
5. monitor task manager Memory column for the tab

What is the expected output? What do you see instead?
The memory allocation increases by at least 1 megabyte per refresh. More 
complex pages increase by more. An example is the IPoSN extension of 
Facebook which increases by 5--10 megabytes per refresh.

What version of the product are you using? On what operating system?
ChromeReload 0.5
Google Chrome 5.0.375.38 beta
Windows XP Pro SP3

Original issue reported on code.google.com by metaed on 19 May 2010 at 9:03

GoogleCodeExporter commented 8 years ago 
This has nothing to do with ChromeReload.
It's a memory-leak in Chromium.
The same thing happens when you reload a page without the extension.
Added a issue to Chromium.
http://code.google.com/p/chromium/issues/detail?id=45498

Original comment by snow.ad...@gmail.com on 31 May 2010 at 9:47

GoogleCodeExporter commented 8 years ago 
WontFix - this is a Chrome problem, as snow.adeka points out. Once it is fixed 
in Chrome it should be fine here,too.

Original comment by nick.lot...@gmail.com on 21 Jun 2010 at 3:40

GoogleCodeExporter commented 8 years ago 
Couldn't chrome-reload work around this chrome memory bug by having an option 
to "refresh" into a new tab. If chrome reload could open a new tab and close 
the last one (as an option), chrome would not have to remember any of the tabs 
history.

Original comment by ecr...@gmail.com on 28 Aug 2010 at 5:08