Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Firefox, Heal Thyself

blog.mozilla.org

Post reply on HN
Print view View original

91–100 of 107 posts

Re: Firefox, Heal Thyself

#91

Post by progrock »

scott_s wrote: post #56
hollerith wrote: post #48

Earlier quoted context omitted.

I wish you could have your GMail, YouTube, etc, and I could have a way to use the internet to access a wide variety of writings without my having to deal with a system so complicated or unreliable that users are being invited to learn a new health-monitoring subsystem for it. ADDED. An argument can be made that my operating system is already a system so complicated or unreliable that it requires its own specialized h…

I think the fact that the world doesn't work like that is inherent, not accidental. Although there are text-only web browsers. But there's a reason I don't use them.

I don't really get the text-only web browser comment.

An aside... If W3m was as fast as Firefox - I'd most likely use it. Bizarre really as you wouldn't expect it to be slower.

Re: Firefox, Heal Thyself

#92

Post by acjohnson55 »

DEinspanjer wrote: post #37
acjohnson55 wrote: post #11

I'm not sure if this applies, but I really hope they provide better tools to identify badly behaving webpages. Sometimes when my CPU or memory are being cranked by Firefox, I really just want to kill the one tab out of 50 that's causing all the problems.

That isn't currently a target area for FHR. Things pertaining to the performance of particular webpages and such are extremely difficult to tease out of the data in a meaningful way. Not to say we will never include something like that in FHR, just not in the first couple of revisions of it. Have you tried out the about:memory page? It doesn't do CPU, but it is a good way to see what particular pages are hogging memo…

I hadn't tried it before. It's interesting and I can see it being helpful in some cases, but it's not immediately easy to parse. I'll probably have to spend some more time with it.

Re: Firefox, Heal Thyself

#93

Post by acjohnson55 »

DEinspanjer wrote: post #37
acjohnson55 wrote: post #11

I'm not sure if this applies, but I really hope they provide better tools to identify badly behaving webpages. Sometimes when my CPU or memory are being cranked by Firefox, I really just want to kill the one tab out of 50 that's causing all the problems.

That isn't currently a target area for FHR. Things pertaining to the performance of particular webpages and such are extremely difficult to tease out of the data in a meaningful way. Not to say we will never include something like that in FHR, just not in the first couple of revisions of it. Have you tried out the about:memory page? It doesn't do CPU, but it is a good way to see what particular pages are hogging memo…

I hadn't tried it before. It's interesting and I can see it being helpful in some cases, but it's not immediately easy to parse. I'll probably have to spend some more time with it.

Re: Firefox, Heal Thyself

#94

Post by dredmorbius »

rangibaby wrote: post #77
dredmorbius wrote: post #76

Earlier quoted context omitted.

Appreciate the response and links. Nice to see there's some work on this. Re: #675539 I'd make unload happen _far_ faster. Within a few minutes, most likely, subject to some user testing to see what impacts/effects are shown. Rather than time the unload, I'd suggest limiting use to some number of active tabs (plus "pinned" tabs). Once that limit is exceeded, start unloading. Resizable windows: the "Bookmark this link…

Re: un-closing tabs, right click on your tab bar choose it from there.

It took me ... a long time to find that. And I am much more keyboard-driven than mouse. Just being able to hit 'u' is awesome.

Other control keybindings often interfere with windowmanger bindings I've been using for well over a decade. The number of competing sets of controls when you start embedding viewers in apps in webpages in browsers in window managers is pretty bad.

Re: Firefox, Heal Thyself

#95

Post by Gmo »

dredmorbius wrote: post #94
rangibaby wrote: post #77

Earlier quoted context omitted.

Re: un-closing tabs, right click on your tab bar choose it from there.

It took me ... a long time to find that. And I am much more keyboard-driven than mouse. Just being able to hit 'u' is awesome. Other control keybindings often interfere with windowmanger bindings I've been using for well over a decade. The number of competing sets of controls when you start embedding viewers in apps in webpages in browsers in window managers is pretty bad.

What about ctrl+shift+T ?

Or I misunderstand what you're talking about.

Re: Firefox, Heal Thyself

#96

Post by Gmo »

com2kid wrote: post #60

My single largest issue with Firefox stability is constantly running into the 32bit memory barrier. Either split tabs out into multiple processes, or enable 64bit support already. My browser crashes on average twice a day due to running out of memory and FF just giving up. It doesn't even crash gracefully, it just up and quits. (I frequently have ~100 tabs open, and I am quite thankful that Firefox lets me search acr…

I have 200+ (sometimes 300+) tabs open, and I never ran in the 32 bits memory limit.

It MUST be an add-on !

Re: Firefox, Heal Thyself

#97

Post by ianox »

progrock wrote: post #83
BrianEatWorld wrote: post #49

Earlier quoted context omitted.

I like this idea. A bit like the pause buttons on my VMs. I have this type of issue more with Chrome than Firefox though and it always seems to be related to leaving a tab open with a video for a long time, even if it isn't being played.

At least with Chrome there is the built in Task Manager.

> At least with Chrome there is the built in Task Manager.

And the about:memory page, which shows you memory usage of all your extensions too.

Re: Firefox, Heal Thyself

#98

Post by com2kid »

progrock wrote: post #90
com2kid wrote: post #65

Earlier quoted context omitted.

> I really can't understand how many people consistently talk about having hundreds of tabs open. What are you so afraid of closing a website for? If it's that important, you will remember to go back to it later. Usually, it's not. Well the hacker news homepage for instance. I typically go down and middle click on any story I find interesting, and the comments section to go with it. This can easily end up with 8-14 t…

I understand how easy that is to do. But when do you have the time to read them? Part of the fun of the web, is getting a little lost in it. But I totally loose focus. Have you ever tried limiting yourself to one window and the judicious use of the back button?

> I understand how easy that is to do. But when do you have the time to read them?

I am a very fast reader. :)

> Have you ever tried limiting yourself to one window and the judicious use of the back button?

Well yes, but then Tabs were invented!

My browsing is like a tree, pages branch off every which way. I used to have to keep track of that entire tree structure in my head, now the browser does it for me!

Re: Firefox, Heal Thyself

#99

Post by com2kid »

cpeterso wrote: post #86
com2kid wrote: post #75

Earlier quoted context omitted.

My issue is, FF climbs up to 2.5GB of memory usage, then it dies. 100% repro. My only add-ons are AB+, Reddit Enhancement Suite, and No Redirect. I am 99% sure this was happening before Noredirect, but I'll try disabling that as well. (Super useful though, wow!) (GreaseMonkey is also installed, but I don't have any scripts loaded in it, disabling it anyway) Of course if you run into the 32bit memory limit, I don't kn…

I wonder if the Reddit Enhancement Suite add-on is the culprit. The "Never Ending Reddit" infinite scrolling feature sounds like it could consume a lot of memory without releasing it. Unfortunately, if the Reddit add-on outlives any reddit.com tabs, it might inadvertently keep those JS objects alive in the background.

> Unfortunately, if the Reddit add-on outlives any reddit.com tabs, it might inadvertently keep those JS objects alive in the background.

With a 64bit memory address space, who cares?

OK so my page file does.

I think I've only given it 100GB or so to play around with, so, sure, if the 32GB of system ram I have available fills up, and all 100GB of my page file get used up, then I'll have to restart FF.

At ~5GB a day of usage, and lets round down for the sake of losses, that is about 20 days of up time before Firefox is denied malloc's by my OS.

Still not great, but a lot better than crashing twice a day!

Re: Firefox, Heal Thyself

#100

Post by dredmorbius »

Gmo wrote: post #95
dredmorbius wrote: post #94

Earlier quoted context omitted.

It took me ... a long time to find that. And I am much more keyboard-driven than mouse. Just being able to hit 'u' is awesome. Other control keybindings often interfere with windowmanger bindings I've been using for well over a decade. The number of competing sets of controls when you start embedding viewers in apps in webpages in browsers in window managers is pretty bad.

What about ctrl+shift+T ? Or I misunderstand what you're talking about.

I've got that hotkey mapped to another function in my window manager.
Post reply on HN