Memory usage gradually grows

[GoogleCodeExporter]

Fauxbar has some sort of memory leak. Not sure where. Opening a Fauxbar tab, 
then closing it, then purging Chrome's memory, shows that Fauxbar gains roughly 
1MB of memory used. Other actions make it use more. And it seems to be 
unrecoverable.

As an interim solution, Fauxbar Memory Helper has been created to disable and 
re-enable Fauxbar when the user's computer becomes idle for a minute or so. Not 
ideal, but better than nothing.

Original issue reported on code.google.com by fauxbar....@gmail.com on 16 Jul 2011 at 9:38

[GoogleCodeExporter]

This is just how it is. Won't fix.

I hope that with Fauxbar 2, I want to use a lot of prototype objects, and make 
things more modular, which will hopefully keep memory usage down...

Fauxbar Memory Helper seems to be working well at least. Good enough for now.

Original comment by fauxbar....@gmail.com on 18 Aug 2011 at 12:46

• Changed state: WontFix

[GoogleCodeExporter]

Original comment by fauxbar....@gmail.com on 18 Aug 2011 at 12:50

• Added labels: Version1

[GoogleCodeExporter]

Re-opening this, in hopes that issue #82 can solve this issue.

But I'll still keep these issues separate, as I think Web Workers can improve 
Fauxbar's responsiveness in some cases, regardless if it solves the memory 
issue or not.

Original comment by fauxbar....@gmail.com on 11 Dec 2011 at 7:28

• Changed state: Accepted
• Removed labels: Performance, Version1

[GoogleCodeExporter]

Issue 82 has been merged into this issue.

Original comment by fauxbar....@gmail.com on 12 Dec 2011 at 4:05

[GoogleCodeExporter]

With Chrome 22, event pages might be able to solve the memory issues:
http://developer.chrome.com/extensions/whats_new.html#22
http://developer.chrome.com/extensions/event_pages.html
http://developer.chrome.com/extensions/runtime.html

Might make Memory Helper redundant!

Original comment by fauxbar....@gmail.com on 28 Sep 2012 at 7:15

• Added labels: Priority-Medium
• Removed labels: Priority-Low

[GoogleCodeExporter]

So when do you plan on implementing FauxBar as an event page? i.e. when can I 
uninstall Memory Helper?

By the way, I love Fauxbar and it is the only reason I could switch from 
firefox to chrome. Good work!

Original comment by mkokotov...@gmail.com on 5 Oct 2012 at 4:28

[GoogleCodeExporter]

One day when I get around to it. I've been pursuing other projects lately and 
haven't found time for Fauxbar. I haven't forgotten about Fauxbar but improving 
it is a low priority at the moment. If I could snap my fingers and make things 
happen instantly it'd be great :\

Original comment by fauxbar....@gmail.com on 25 Oct 2012 at 9:39

[GoogleCodeExporter]

This feels like a big task, but I think it's time. Or at least time to try :D

Basically need to sift through background.js and move things into:
- chrome.runtime.onStartup
- chrome.runtime.onInstalled
- or just on an event page

Original comment by fauxbar....@gmail.com on 11 Jul 2013 at 2:55

• Changed state: Started

[GoogleCodeExporter]

Code has been added to v1.4.0 to make Fauxbar Memory Helper redundant.

But unfortunately, I've had to comment out this code because of a really 
annoying Chrome bug:
https://code.google.com/p/chromium/issues/detail?id=260981

Fauxbar can call `chrome.runtime.reload()` on itself to reset its memory, but 
because of this Chrome bug linked above, the Omnibox gets resized; it's 
horrible.

So once the Chromium team fixes their bug, I'll update Fauxbar and give Memory 
Helper the boot. At the moment, they're aiming for Chrome 30, so could be a few 
weeks away still.

Original comment by fauxbar....@gmail.com on 18 Jul 2013 at 4:34

• Changed state: Accepted
• Added labels: Priority-High
• Removed labels: Priority-Medium