Jump to content

Wikipedia:Reference desk/Archives/Computing/2018 December 6

From Wikipedia, the free encyclopedia
Computing desk
< December 5 << Nov | December | Jan >> December 7 >
Welcome to the Wikipedia Computing Reference Desk Archives
The page you are currently viewing is an archive page. While you can leave answers for any questions shown below, please ask new questions on one of the current reference desk pages.


December 6

[edit]

Limitations on Running Very Large Number of Chrome Windows simultaneously ?

[edit]

Is there a practical or theoretical limit on running a very large number of Google Chrome windows simultaneously under Windows 10 on a desktop machine with 12 Gb of main memory? Does running a very large number of Google Chrome windows simultaneously lead to a risk that Chrome can shut down suddenly? Robert McClenon (talk) 05:16, 6 December 2018 (UTC)[reply]

Are we talking about a couple of hundred tabs or a couple of thousand? And do you have google chrome background tab throttling[1] enabled or disabled? --Guy Macon (talk) 08:46, 6 December 2018 (UTC)[reply]
Here[2] is a fellow who did some tests and found:
  • A typical 8GB RAM and i7 Processor can crash out your google chrome for around ~9600 tabs.
  • If you have 4GB RAM and cheap processor than it can crash out at ~8000 tabs.
  • After I pass about 50 tabs, I can no longer see the favicons that help me distinguish tabs apart.
  • When nearing 70 tabs, I can no longer see any text from the page title; all I see is 70 little bumps.
  • The first 3k can be opened in less than a minute, but as you get close to 10k it takes about a second per tab.
--Guy Macon (talk) 08:53, 6 December 2018 (UTC)[reply]
This might not be entirely representative, the guy just opened google.com 10,000 times. Chrome might have parallelized some of this under the hood, and Google's homepage is much less demanding than the average website. I think if you opened something very simple, like a standard 404 page on Apache, you could probably get even more tabs.
Well, first, you can see what tab you are on by hovering over it. Second, the slowing down will predictably occur when the browser frames can no longer all reside in physical memory. Robert McClenon (talk) 02:00, 8 December 2018 (UTC)[reply]
FWIW, not what you're asking, but I use Waterfox and I've found that 1,000-2,000 tabs (of different webpages) work just fine on 16 GB and probably a lot more would work too but I have to restart it occasionally because it tends to fill up the RAM over the course of a week or two. 93.136.105.185 (talk) 09:56, 6 December 2018 (UTC)[reply]
I am using about 50 tabs, not hundreds or thousands. I wasn't aware of the background tab throttling feature, so I am using whatever is the default. The Chrome crashes to which I am referring happen suddenly and seemingly randomly. When I launch Chrome again, it restores the tabs. Chrome isn't always able to restore the tabs if Windows crashes, but that is a different question. (As to telling the tabs apart, they identify themselves when hovering with the mouse cursor.) That is, with about 50 tabs, the performance is typically fine, and then Chrome suddenly disappears. Robert McClenon (talk) 00:53, 7 December 2018 (UTC)[reply]
Sorry for more unwanted Mozilla-based browser promotion, but Firefox/Waterfox/Pale Moon with Session Manager addon has always managed to restore the tabs for me, even if power failed, and I never get crashes any more (used to have a lot with Firefox until a year or two ago, probably when I switched to Firefox ESR and then Waterfox). Maybe Chrome also has an "extended support release" program. I find staying at the bleeding edge is rarely worth it with browsers. 93.136.49.90 (talk) 06:37, 7 December 2018 (UTC)[reply]
What is happening to me is that, apparently randomly, Chrome just disappears suddenly. That does seem to give back the memory. (I know that it should give back the memory. I also know that memory is not always as neatly managed as it should be.) Robert McClenon (talk) 02:00, 8 December 2018 (UTC)[reply]

Removing apps that can not be un-installed from Windows 10 "Apps & Features"

[edit]

My "Apps & Features" include such "dead" apps.

I have tried the regedit method ( HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Uninstall) but none of these apps appear there.

אילן שמעוני (talk) 08:55, 6 December 2018 (UTC)[reply]

I just did something I loath to do - going over the entire registry and deleting all keys that include the dead apps names. It did remove them from the uninstall list. I hope I didn't do any damage.
אילן שמעוני (talk) 21:25, 6 December 2018 (UTC)[reply]
You could always just ignore them. You definitely should back up the Registry before editing it. In Windows 10, you could also try the "Windows Reset" feature, which reinstalls Windows without deleting your personal files. (You should still back them up anyway, and make regular backups as a matter of course, since plenty of things can cause data loss.) --47.146.63.87 (talk) 22:01, 6 December 2018 (UTC)[reply]