zoom314a wrote:Ver Greeneyes wrote:@zoom314a Does about:memory show where the memory is going? Do you have any ghost-windows? I assume since you're calling it a leak that the memory sticks around even if you close all tabs (otherwise you might want to consider using a different word). If about:memory shows a high amount of heap-unclassified, you could try running with DMD, though you'd have to build the browser to do that.
Since I have no idea on how to use a compiler and no extra income to use buying a compiler, DMD can go to heck, I'm not a programmer and the link says the following about DMD in Win64.DMD currently doesn't work properly on Win64; it gives empty stack traces and so the output is useless.
DMD in Win64 currently is a Wild Goose Chase...
Now I did the 'about:memory', I clicked on the left most button, called 'Measure' and the biggest is:
1,100.32 MB (34.79%) ++ (108 tiny)
This is composed of 108 tabs for websites, some are for banking and such, some are like here, and then there are the following 6:
├─────22.59 MB (00.71%) ++ top(chrome://browser/content/browser.xul, id=3)
├─────12.57 MB (00.40%) ++ top(none)/detached
├─────12.54 MB (00.40%) ++ top(about:memory, id=74398)
├──────1.55 MB (00.05%) ++ top(about:newtab, id=267)
├──────0.15 MB (00.00%) ++ top(about:blank, id=7)
└──────0.15 MB (00.00%) ++ top(about:blank, id=9)
Now 108 has become 112... Yeah I closed two tabs since I started this reply, I had a big furry interruption from the real world here, I have a big cat.
├──1,257.15 MB (35.95%) ++ (112 tiny)
├─────31.21 MB (00.89%) ++ top(none)
├─────29.12 MB (00.83%) ++ top(chrome://browser/content/browser.xul, id=3)
├──────1.48 MB (00.04%) ++ top(about:newtab, id=267)
├──────0.15 MB (00.00%) ++ top(about:blank, id=7)
└──────0.15 MB (00.00%) ++ top(about:blank, id=9)
Oh and for the record, memory leak is not My term, it's what everyone else calls it, since more and more memory is consumed by the browser, I have no real term for this.
I'm more concerned that the browser just keeps on getting bigger and bigger as the day wears on, with the crash that I know is coming, the oldest nightly x64 browser that I remember is Minefield, that one may or may not have had a leak(or whatever you'd like to call it), but then I don't know where Minefield fits in, outside of being a long time back.
As to the cause of the sluggishness, that could be a long story that may or may not mean a thing when it comes to the browser and might be a separate issue.
Uh mate that is not a memory leak. Unless you see like 1GB in "heap unclassified" or something else, it looks normal for having 100+ tabs open. I'm really not sure what point you're trying to make