What is meta? ×
Meta Stack Exchange is where users like you discuss bugs, features, and support issues that affect the software powering all 131 Stack Exchange communities.

Not sure if someone is looking into this issue but in case you keep refreshing the review -> first question page on StackOverflow you will notice memory increase. I got more than 1GB used by stackoverflow 1 tab only.

enter image description here

Steps to Reproduce: As someone suggested that it is not reproducible on their machine, I tried to reproduce the issue and found it reproducible in new window of chrome.

To reproduce, goto Review->First Posts page not Review only and then keep pressing F5 for sometime. Check windows task manager or chrome task manager. There is significant increase in memory used by tab. (changed from ~50mb to ~150mb in just 5-6 refreshes).

My machine config: Windows 7 (64bit), i5 proc, 4GB ram

Additional details I have configured chrome to reload last session tab on start (not sure if helpful). Also here is the complete chrome task manager capture (tried again to reproduce in new window and successfully reproduced):

Reproducible Bug

UPDATE: I tried to reproduce it on FireFox and it was not reproducible there. First memory goes up to 150MB but after that cleaned up again. Not able to reach even 170 MB. So seems like an issue with Chrome instead of stackoverflow.

share|improve this question
    
Something's weird, but I'm not observing it when I hit the page - I only get 77MB usage on the page. For comparison, I get 55K when I'm on this page. –  Makoto Apr 14 '13 at 16:44
    
Hmm... I am not sure what was the reason but I spent good time in analyzing which tab is culprit and found it is the stackover flow only. Previously it was around 800MB then refreshing page led to 1Gigs+ –  Rohit Kandhal Apr 14 '13 at 16:51
    
And most of the time I was refreshing the review page and reviewing the questions (on same tab) –  Rohit Kandhal Apr 14 '13 at 16:52
    
I tried refreshing/reviewing and could not get the tab at more than 40MB (and lowest score is around 29MB). But still a weird problem. –  Hugo Dozois Apr 14 '13 at 17:19
    
Hmm, I seem to remember someone bringing up something similar on another Meta. Can't seem to find it. –  Bart Apr 14 '13 at 17:27
    
What browser plugins are you using? –  George W Bush Apr 14 '13 at 17:36
    
Adblock, Google Calendar, Google Dictionary, Google URL shortener, Chrome to phone –  Rohit Kandhal Apr 14 '13 at 17:39
1  
Would you try it in another browser? A browser page doesn't persist data between refreshes. It's more likely a Chromium bug. –  bobobobo Apr 14 '13 at 18:57
    
@RohitKandhal Chrome has been developing memory leaks recently. I've moved away from it until they're resolved. That being said, I just looked into this with Firefox, and am not having memory leaks. –  Emrakul Apr 14 '13 at 19:06
    
Will surely try. –  Rohit Kandhal Apr 14 '13 at 19:37
    
@bobobobo What about session storage? That persists throughout your session –  Cole Johnson Apr 14 '13 at 22:09
    
Session is just a single cookie identifier passed between the browser and the server on each request. The session data however is stored on the server. Apparently the max size of the cookie data is 4093 bytes? –  bobobobo Apr 14 '13 at 23:00
    
I've been seeing Firefox run up memory (leading to one crash and several locks) with SE usage in the last few days. Over the weekend I thought it was the new version of Firefox I picked up, but I saw the same problem at work where IT doesn't allow automatic updates. I said something about that in some chat room, looking to see if it was happening to anybody else, but I can't characterize it yet so I haven't posted about it otherwise before this comment. (My problem seems to implicate chat, so may be different.) So, I guess switching to Chrome might not help me? :-) –  Monica Cellio Apr 16 '13 at 17:46

You must log in to answer this question.

Browse other questions tagged .