what is the difference between load tab and show tabs
Can someone tell me the difference between show all tabs from last time and load tabs. I'm trying to figure out why Firefox slows down and eventually crashes. I have close to 300 tabs but I have clicked on only a few. The rest I though were dormant. Still after a few days FF slows down. The last time I decided to restart FF I clicked on File and waited 17 minutes for the drop down menu that let me click on Exit. 23 minutes later FF crashed. So whatever is going on in the background has to be involved with why this is happening. The FF interface by the way had been closed for about 20 minutes before I got the crash notice. This is not about running MBAM,buying a new machine or upgrading to the ESR. to fix the problem. It's academic. i want to know why because all the recommendations to upgrade in the past have not improved the situation and recent upgrades made things worse. I will be doing the ESR upgrade in time but I want to be able to launch this version as well perhaps as a different user.
Gekose oplossing
There is a page, but I haven't studied it, so I don't know how helpful it is: https://developer.mozilla.org/docs/Mozilla/Performance/about:memory
Lees dié antwoord in konteks 👍 0All Replies (8)
show tabs, to view and know what tabs you closed recently.
load tabs, OPEN ALL tabs you closed recently.
so its SHOW & RE-OPEN
There are browser.sessionstore.restore prefs where you can set how tabs from the previous session are restored.
- browser.sessionstore.restore_on_demand
- browser.sessionstore.restore_pinned_tabs_on_demand
- browser.sessionstore.restore_tabs_lazily
You can open the about:config page via the location/address bar. You can accept the warning and click "I accept the risk!" to continue.
DavidSorge said
Can someone tell me the difference between show all tabs from last time and load tabs.
I haven't seen Firefox 51 for a long time. Are these choices on the Options page or somewhere else? Can you post a screenshot?
I'm trying to figure out why Firefox slows down and eventually crashes. I have close to 300 tabs but I have clicked on only a few. The rest I though were dormant. Still after a few days FF slows down. The last time I decided to restart FF I clicked on File and waited 17 minutes for the drop down menu that let me click on Exit. 23 minutes later FF crashed.
When 32-bit pre-Quantum Firefox gets near its maximum memory usage, it becomes super-slow and unresponsive. This is just a problem that I don't think has any solution. You certainly could keep an eye on it in Task Manager's Processes tab, or try exiting Firefox more regularly.
The FF interface by the way had been closed for about 20 minutes before I got the crash notice.
Should be more like 1 minute to get the Mozilla Crash Reporter if the system is not tied up...
Are you running XP or is that information erroneous?
I'm still on XP. Do you know what FF is using the memory for? Even when I'm working somewhere else FF continues to eat memory.
DavidSorge said
I'm still on XP. Do you know what FF is using the memory for? Even when I'm working somewhere else FF continues to eat memory.
If you type or paste about:memory in the address bar and press Enter to load that internal page, you can access some tools to view how memory is being used, but it is quite verbose so it's difficult to use the page for a quick overview.
jscher2000, Sorry I've taken so long getting back to you. I'll take a look at about:memory. Well I looked and it has lead to many more questions. Is there a tutorial about it.
Gekose oplossing
There is a page, but I haven't studied it, so I don't know how helpful it is: https://developer.mozilla.org/docs/Mozilla/Performance/about:memory
jscher2000, Hi. The page that you refereed me to do have quite a bit to offer. And I'll be up late at night for a while trying to understand them. One thing that stands out is that it doesn't appear that it gives enough detail to Know what to get rid of. There is a Free Memory button that looks intriguing but the part about freeing caches scares me. I'm going to read the MDN web doc before I tackle the about:memory page. This is just a problem that I don't think has any solution. I'm troubled with the idea that there may be no solution and I hope that's not the case. I may want to return to this but for now I'll mark it solved. Thanks for the help
