Log in

Tue, May. 13th, 2008, 12:09 pm
Process list for my new OS

The web browser is the new operating system. My own computer is at this point little more than a glorified web browser, with a text editor, command prompt, python interpreter and svn thrown in for the occasional color.

Since the web browser is the new OS, it should really, really, have the equivalent of a process list. I almost always have a whole bunch of tabs open, and firefox is most of the time using a nontrivial amount of CPU doing not much of anything. I have to guess which tab is causing the problem when the CPU gets pegged, and sometimes it seems that even shutting down all tabs doesn't completely fix the problem. Could somebody please implement metrics on how much CPU each tab/window is using, and get the process separation right so that whenever a tab/window is shut down all remnants of it are completely toast?
(Deleted comment)

Tue, May. 13th, 2008 11:16 pm (UTC)

Firefox uses Gecko, Safari uses Webkit. Very different.

Tue, May. 13th, 2008 07:43 pm (UTC)
megadog: One Website, One Browser-session.

My hate about web-browsers is that - to my knowledge - *none* of them will launch an entirely-separate standalone instance of themselves when you click on an embedded link.

I want to keep my processes entirely separate and without inheritance: so that when I'm browsing my chosen porn in one window, watching a movie in another and am doing online-banking in another, the browser-sessions are totally oblivious of each other.

No shared cookies; No shared session-credentials; If one browser-session stalls I want to be able to kill it without compromising other browser-sessions.

50 instances of 'firefox.exe' in my process-table? Sure! So long as they do not know of each other.

Wed, May. 14th, 2008 12:14 am (UTC)
chouyu_31: Re: One Website, One Browser-session.

One of the reasons why browsers don't do "one website per window" is a matter of implied shared state. For example, say you were browsing Facebook, and decided to open up a few buddies in alternate windows (your tab bar is being overloaded, maybe these are special, maybe you want to compare, whatever). If new window implied new session (with different cookies, etc.), then you wouldn't be able to view them. Even worse, when you started to close down windows, which cookies would you save? Which browser history would you save? Which bookmarks would you save? There are reasonable answers to each of these questions, but for every reasonable answer, there are users that will claim that your answer is wrong.

Also, I don't know about you, but Firefox on my machine easily eats 100-400 megs, and 50 browser processes would easily run me out of memory.

I understand where you are coming from though, which is why I have IE tab for Firefox (for secondary gmail, hotmail, yahoo, etc., sessions), and Opera.

Wed, May. 14th, 2008 12:14 am (UTC)

A-fucking-men. It's usually a screwed up plugin or crappy JavaScrap code that causes browser windows to hang. Plugins can't be trusted, and JavaScript absolutely can't be trusted. We should be able to nuke them with extreme prejudice the same way we nuke hung processes.

Wed, May. 14th, 2008 05:57 pm (UTC)
jeffdaly: Mozilla is working on it - see Firefox extension PluginWatcher

There actually is some work being done in Mozilla to address this sort of thing. Firefox 3, which is currently still in development (but nearly done) includes XPCOM hooks for monitoring plugin performance with nsIObserverService. See bug 412770 for details on how it came about. Fima Kachinski has authored an addon, Plugin Watcher that implements the service and displays a load meter in the status bar. It could use a lot more work, but at least it's a start.

Personally, I'd like to see something in the style of Firebug's Network Monitoring Traces. But should observe all the tabs loaded in the browser, and break down the activity to show which addon, plugin or native piece of code is hogging the CPU.

Thu, Aug. 14th, 2008 04:56 pm (UTC)
zaitcev: Re: Mozilla is working on it - see Firefox extension PluginWatcher

Plugins are only a small part of the problem. More commonly there's an issue with JavaScript or other inside one of the tabs and you have to close half of them before lucking upon the one that hogs the CPU. IMHO, per-tab separation is more important than per-plugin separation.

Wed, May. 14th, 2008 08:41 pm (UTC)
misterajc: Non browser applications

I still have a few applications that are not browser based. Though in some cases there are web versions these are usually slower or less powerful. Email, instant messaging, photo and video editing, spreadsheet, SSH terminal program and oh, yes, bittorrent client are all their own applications. I suppose I could go over to some webmail application but there are times when I want to read and reply to email when I don't have a net connection.

Fri, May. 23rd, 2008 04:35 am (UTC)

Maxthon browser does this automatically. I allows you to shutdown hung or high CPU .using js sites. It's a little buggy, but no more so than Firefox

Mon, Jan. 26th, 2009 03:19 am (UTC)

I'll have to try Maxthon out, thanks.

Mon, Jan. 26th, 2009 03:15 am (UTC)
chessknught: Google Chrome OS

I can see Google moving that way. I'm a chrome user, and I wouldn't be surprised if they added something like that to the Google Toolbar (although for some reason it isn't useable in Chrome yet).

Cheers. :)