News for hackers. Stuff that matters.
Re:Chrome 55 uses 30% less memory than 54 by ausjke on Saturday December 03, 2016 @03:36PM (#13097386)
awesome news then, chrome really needs to improve memory usage, especially when I have lots of tabs open.

under firefox I normally had 120 tabs open all the time, and it's fine. with chrome, I dare not to exceed 60 tabs. chrome triggers heavy swap all the time still, which renders the system very sluggish.

Re:Chrome 55 uses 30% less memory than 54 by nazri1 on Saturday December 03, 2016 @06:46PM (#13098051)
My laptop has no ssd. This sluggishness brings back memories of linux trashing the swap partition when it ran out of memory back in the early 2000s. Quite understandable since back then most people don't have that much RAM (64Mb?). Nowadays I have 8Gb on my laptop and I run linux with swap disabled. The only disk trashing that I'm having nowadays is due to chrome, and it's definitely not due to swap but the effect is almost the same - at best the laptop is unusable for up to 30 seconds, at worst, I have to do a hard reboot because that's the only way to recover - I can't even switch to a new terminal to kill chrome. Attempts to log in via the tty console (Ctrl+Alt+F2) in order to kill chrome is futile. I could enter the username, but the password prompt took forever to appear. Most of the time it expires after 60 seconds. If I manage to enter the password, the shell prompt can take forever to appear.

Nowadays I do a "killall chrome; sleep 2; killall chrome" whenever it starts to trash the disk and giving me the bad vibe.

Re:Chrome 55 uses 30% less memory than 54 by kofejnik on Saturday December 03, 2016 @08:49PM (#13098389)
put chrome cache on a ram disk, helped me a lot last time I had a spinning hdd
Re:Chrome 55 uses 30% less memory than 54 by jcoffland on Saturday December 03, 2016 @04:34PM (#13097609)
This is mainly because Chrome allocates a process for each page whereas FF only allocates a thread. The important factor being that threads share an address space where processes are allocated their own and thus consume more memory. Separate processes are arguably more secure and of one process crashes it does not take down the whole browser but all this comes at a cost. This cost is very apparent with many tabs open.
Re:Chrome 55 uses 30% less memory than 54 by fulafel on Sunday December 04, 2016 @01:05AM (#13098973)
The primary security gain of sandboxing is about making it harder for web content to hijack your computer by exploiting security bugs. Many common types of bugs can be exploited to get remote code execution in browsers because of unsafe programming languages used (C/C++).

Both Chrome and Firefox have multi-process sandboxes now, Firefox is a little behind and plans to enable multiple content processes next year.

While Chrome's is more granular, it does share processes between web pages from the same domain so won't start a new one for quite every tab.

Re:Chrome 55 uses 30% less memory than 54 by strcat on Tuesday December 06, 2016 @10:41PM (#13120296)
They're shared among site instances, not the same domain. It has to do with web standard semantics. Google has been working on https://www.chromium.org/developers/design-documents/site-is... for quite some time which will probably ship in 2017. That's the next step beyond the --process-per-site-instance after --isolate-extensions.

Firefox is more than just a little bit behind when it comes to sandboxing though... there's a LOT more to sandboxing than splitting up processes. That doesn't result in any meaningful isolation without a lot of further work, and improving sandboxing is a major undertaking that Chrome has been working on for years.

Re:Chrome 55 uses 30% less memory than 54 by robotresearcher on Saturday December 03, 2016 @05:33PM (#13097826)
> processes are allocated their own and thus consume more memory.

Copy-on-write means this needn't be a large overhead. Only pages that change after forking are duplicated.

Re:Chrome 55 uses 30% less memory than 54 by mortehu on Sunday December 04, 2016 @11:18AM (#13100411)
But the OS is committing to supplying memory for any writable pages you duplicated, because after all you might write to them. The OS doesn't know which pages you won't duplicate.

Unless you set your vm.overcommit_memory sysctl variable to 1 (= never refuse malloc), duplicated writable pages are going to subtract from available memory, even if all copies are currently the same.

Re:Chrome 55 uses 30% less memory than 54 by robotresearcher on Tuesday December 06, 2016 @10:20PM (#13120190)
Sure. So your memory usage is reported as high but might not be actually high. Some sophistication is needed to interpret resource counts.
Re:Chrome 55 uses 30% less memory than 54 by weaksauce on Saturday December 03, 2016 @07:56PM (#13098245)
I made a simple firefox/chrome extension for people that horde tabs as temp bookmarks. You might find it useful to find tabs and quickly navigate to them by clicking on the link in the list. It's free and open source. The github page has a gif showing usage. You can also type cmd-shift-e or ctrl-shift-e to switch to it.

Chrome Extension: https://chrome.google.com/webstore/detail/tabist/hdjegjggiog...

Firefox Extension: https://addons.mozilla.org/en-US/firefox/addon/tabist/

source code: https://github.com/fiveNinePlusR/tabist

Let me know if you find it useful or have any suggestions. (patches are awesome too)

Re:Chrome 55 uses 30% less memory than 54 by sunnyps on Sunday December 04, 2016 @05:08AM (#13099462)
In Chrome you can press "Ctrl/Cmd + Shift + D" and bookmark all open tabs into a folder. Then you can right click on the folder later to open all those tabs.
Re:Chrome 55 uses 30% less memory than 54 by kilroy123 on Saturday December 03, 2016 @05:17PM (#13097771)
I can't recommend this extension enough, The Great Suspender:

https://chrome.google.com/webstore/detail/the-great-suspende...

It freezes your tab after a set amount of time, freeing up the memory for each tab.

Re:Chrome 55 uses 30% less memory than 54 by raarts on Saturday December 03, 2016 @06:34PM (#13098021)
And it's also a huge battery saver.
Re:Chrome 55 uses 30% less memory than 54 by thejay on Saturday December 03, 2016 @03:54PM (#13097447)
I too keep a lot of tabs open. I use OneTab and The Great Suspender chrome extensions to also keep memory usage under control. They've been indispensable tools for the tab hoarders like me.
Re:Chrome 55 uses 30% less memory than 54 by ilaksh on Saturday December 03, 2016 @05:50PM (#13097880)
Exactly. Its hoarding. So eventually they will have to build in features to protect hoarders from themselves.
Re:Chrome 55 uses 30% less memory than 54 by ausjke on Saturday December 03, 2016 @04:21PM (#13097551)
great, did not know this, I do use clutter-free extension all the time which avoids the same URL on multiple tabs.
Re:Chrome 55 uses 30% less memory than 54 by curiousgal on Saturday December 03, 2016 @03:38PM (#13097398)
120 tabs?! What for?!
Re:Chrome 55 uses 30% less memory than 54 by spacehacker on Saturday December 03, 2016 @03:50PM (#13097431)
I personally use tabs like a desktop with all kinds of papers, documents and books flying around. Sort of like this:

https://s15.postimg.org/dpq7mpmaz/messydesk.jpg

Re:Chrome 55 uses 30% less memory than 54 by srathi on Sunday December 04, 2016 @02:22AM (#13099145)
That seems like Einstein's desk. Is that correct? I remember seeing this picture before.
Re:Chrome 55 uses 30% less memory than 54 by setq on Saturday December 03, 2016 @03:40PM (#13097404)
I do this. It's a curse. I don't know why.
Re:Chrome 55 uses 30% less memory than 54 by Buge on Saturday December 03, 2016 @04:09PM (#13097499)
I once had 1000 tabs open in firefox. I only found out when I accidentally clicked the x and it asked "are you sure you want to close 1000 tabs".
Re:Chrome 55 uses 30% less memory than 54 by Theodores on Saturday December 03, 2016 @06:35PM (#13098025)
Sometimes I open 100 or so tabs to do repetitive stuff I cannot code, data entry work that won't be easily automated or needs the human touch, e.g. updating a product catalogue. On top of the 10-50 tabs open that gets to be a lot of heavy pages but makes for an efficient workflow. With hot keys and 'close all tabs to the right' I can quickly get through a lot of stuff that needs attention to detail and focus to get done.

All I am saying is that there are situations when a lot of tabs is the best option given the circumstances, e.g. lots of data entry work.

Re:Chrome 55 uses 30% less memory than 54 by wiredfool on Saturday December 03, 2016 @03:44PM (#13097417)
Tabs are the new bookmarks.
Re:Chrome 55 uses 30% less memory than 54 by sker on Saturday December 03, 2016 @04:26PM (#13097572)
They're better. If I bookmark something with any service, chances of me ever checking that out again drop to nearly zero.

Tabs, by virtue of being there bugging you, are bookmarks, to-do lists, and task reminders all in one.

Re:Chrome 55 uses 30% less memory than 54 by truth_sentinell on Saturday December 03, 2016 @07:07PM (#13098121)
No, they aren't. I don't know about you, but I can't have more than 20 tabs open and consciously be aware of the content. I can't think of people like above, having 120 tabs. It's probably a waste of time and resources. First because you can't possibly hold in your memory 120 tabs, thus you'll have to visit them or read the title to remind you why is it there on the first place. With bookmarks at least you can use the search bar...

So it ends up being counterproductive.

Re:Chrome 55 uses 30% less memory than 54 by xorxornop on Saturday December 03, 2016 @09:25PM (#13098490)
Naw, at least with me I seem to be able to by treating the tab ordering as a conceptual discovery ordering. That is, I remember what things I learned / researched prior to and following each tab. It's lossy, but because each has a unique relationship with its surrounding concepts there's plenty of opportunities for parity-like behaviour; redundancy.

When researching a thing I'll open up some high level page about it, then do breadth-first searches of tab contents, opening up new tabs whenever I see something that looks interesting, has wider implications, or possibly has some weaker relationship to a thing with one or both of those properties and I think I might be able to traverse the concept graph this way to find it / them.

So I end up with a sort of flat tree where it corresponds almost directly to my earlier thought graph which produced them. I can work with maybe 200 this way... But not more. Unless I open them in different windows - sometimes different browsers, actually, to help further differentiate/compartmentalise them (eg. I'll use this strategy for largely disparate topics). Then, well, I'm not sure where I top out, all I can say is I once crashed my box from out of memory (not running swap), and it's a 32GB box soooo... I dunno.

There are likely many others that work this way. Perhaps it's not common, but I also feel that it's very unlikely unique!

Re:Chrome 55 uses 30% less memory than 54 by truth_sentinell on Sunday December 04, 2016 @08:38AM (#13099933)
You gave me an idea to a chrome plugin to manage tabs. I'm gonna open ne some tabs to learn how to write plugins.
Re:Chrome 55 uses 30% less memory than 54 by tokai on Saturday December 03, 2016 @10:47PM (#13098692)
I do the same. I also try to organize my bookshelf in the same fashion.
Re:Chrome 55 uses 30% less memory than 54 by _nedR on Sunday December 04, 2016 @12:39PM (#13100790)
For me session manager sessions (in firefox) are the new bookmarks.

i try to split different fields of interest into separate windows. Then i save that window as a suitably titled session and close the window. If i need to add a new tab to a session, i use the "append to session" feature. That way i dont clutter up my bookmarks or my primary firefox session.

Re:Chrome 55 uses 30% less memory than 54 by tdkl on Saturday December 03, 2016 @04:14PM (#13097524)
Sadly they aren't bookmarks and then people moan about memory usage, when they should get a reality check instead.
Re:Chrome 55 uses 30% less memory than 54 by to3m on Saturday December 03, 2016 @05:03PM (#13097730)
I don't know if you're familiar with the ins and outs of writing computer programs, but it's actually often practical to make a program that does one thing do another instead. So in this case one obvious thing that could be done is to have a dormant-type (exact terminology TBC) tab.

Such things would have an entry on the tab bar like a normal tab, but wouldn't actually have anything loaded until you clicked. Firefox already supports this sort of thing internally, it looks like, since when you reload a session that had a bunch of open tabs, it doesn't seem to load each tab's contents until you click on it.

(Open such a thing with a particular shortcut, or by transforming an existing tab into a dormant one - obviously equivalent in terms of JS callbacks and so on to closing the window.)

Other possibilities could include multiple types of tabs, and/or alternative UIs for lists of pages you like/pages you want to look at sometime soon.

Re:Chrome 55 uses 30% less memory than 54 by curiousgal on Saturday December 03, 2016 @05:36PM (#13097831)
>it's actually often practical to make a program that does one thing do another instead

Like using Photoshop to abort a system shutdown if you forgot to commit.[0]

0.https://www.quora.com/What-are-the-greatest-software-misuses...

Re:Chrome 55 uses 30% less memory than 54 by hugodahl on Saturday December 03, 2016 @10:10PM (#13098609)
On Windows, using the built in notepad, you can block any shutdown by having an instance pen with any unsaved changes. Handy when Windows schedules a reboot and you've got your debugging session setup just right.
Re:Chrome 55 uses 30% less memory than 54 by Tempest1981 on Sunday December 04, 2016 @04:19AM (#13099371)
I read that Win10 will still force a scheduled reboot, even with unsaved documents: https://www.reddit.com/r/sysadmin/comments/3hb614/windows_10...
Re:Chrome 55 uses 30% less memory than 54 by robotresearcher on Saturday December 03, 2016 @05:36PM (#13097833)
Now we know how people behave we can engineer the software to work well for them. Suspend the LRU tabs so they can be paged out, etc.
[dead]
Re:Chrome 55 uses 30% less memory than 54 by sctb on Sunday December 04, 2016 @01:04PM (#13100928)
We've banned this account for repeatedly violating the guidelines after we've asked you to stop. This account has posted a lot of decent comments, so we'd be very glad to unban it if you email [email protected] and we believe you'll stop breaking the guidelines.
Re:Chrome 55 uses 30% less memory than 54 by grzm on Saturday December 03, 2016 @06:54PM (#13098077)
go fuck yourself

Please don't be uncivil on HN, regardless of the discussion.

Re:Chrome 55 uses 30% less memory than 54 by reactor on Saturday December 03, 2016 @08:33PM (#13098337)