Link Details

If you don't vote, who will? Login and vote now.
Link 111237 thumbnail
User 259587 avatar

By raasiel
via shafqatahmed.com
Submitted: Sep 06 2008 / 16:06

I was going to replace Flock with Google Chrome, but I had refrained from doing because huge memory usage of the Chrome browser
  • 1
  • 1
  • 164
  • 47

Comments

Add your comment
User 111696 avatar

bloid replied ago:

0 votes Vote down Vote up Reply

surely, this is the whole point?

The model for Chrome is process based not thread based so you don't get this issue, but the footprint is larger.... All old browsers were thread based as they can then have a smaller footprint (and this was seen as a better thing), but the javascript from one site can bring the whole browser down...

It's swings and roundabouts, and unfortunately I don't see how there can be any happy middle ground unless someone comes up with a dramatic change to the way things are done

Add your comment


Html tags not supported. Reply is editable for 5 minutes. Use [code lang="java|ruby|sql|css|xml"][/code] to post code snippets.

Voters For This Link (1)



Voters Against This Link (1)