FF2 eats the big one

Anyone been getting these problems? Every once in a while, firefox's cpu usage shoots up to ~75% for no particular reason, and stays there.

not sure why at all, I have a suspicion it's flash, but the thing doesn't actually crash.

closing and re-opening makes things lovely again.

I've also had the thing magically open a new tab as some sort of floating window, display for a few moments, then crash out.

bloody annoying.

come to think of it, it started after I realized I was still using the beta version of the flash plugin, deleted all the old libflashplayer.so files, and installed again from the adobe website.

stupid adobe.

 

No, I haven't had any odd behavior on Vista, XP, Ubuntu, Pardus, or Arch recently. Well, besides recently closed tabs not working on the Ubuntu build. Try using the flashblock plugin for awhile and see if it goes away. Also, the fasterfox extension has a block for a flash popup 'exploit', it may help.

I use the term 'exploit' very loosely above.

 

yeah, that's selected... it's not an actual pop-up, it would be something like I clicked a link on a webpage, things would stop responding for a bit, then this extra window without any of the navigation stuff would pop up, display the page I clicked to, then the thing crashes... very much argh.

 

Never had that problem under Feisty, BigV.

I know that whenever I open say, Rhythymbox, a word processing program, a console and a few FF windows (with a few tabs in each window), FF will crash sometimes.

 

The Only problem I have with FF2 on Ubuntu is whenever I right click the tab bar ....... I have no choice but to click a option or the menu will not go away. This sometimes forces me to click New tab button.

 

I can't say I've had a problem like this w/ Firefox on Ubuntu. It's not extremely stable (and IMO FF has been getting less stable since v1.0.7), but it's never given me that type of problem. It'll just crash every now and then.

 

I had that problem once before, I can't remember when or where, though...
I'll try to remember more details.

Edit: Well, let's make sure we're talking about the same thing. You click on a link, even a link that you click regularly and always opens in the same window and tab. The main window goes blank, and spawns another window with the page in it. If you close the new window, the original window either crashes or remains unusable untill you 'killall firefox-bin'

I had this problem in Arch for awhile, I'm trying to remember when. Honestly, I don't think I ever fixed it, but it wasn't happening often enough to worry that much.

You could try removing your distro's packaged version and use the installer from Mozilla's site. Also removing your profile and starting over might help. Of course, it could be an extension, too, which are you using? I think at the time I was probably using adblock, filterset.g updater, openbook, and translate. I might have been using another I can't remember the name of, to edit the content of menus.

 

Actually, come to think of it, I had been having this problem with one particular site, but it's a rather low-importance local site that I don't visit anymore. But every time I would click a link it would open a new window and then FF would crash. I think it was happening back in Edgy with FF2. I didn't have any extensions or themes installed either.

 

Yeah, certain memory intensive sites will crash FF2.0 in Linux. Then again, they can also crash FF2.0 under Windows...so its about the same.

 

hmmm, at least I'm not going completely crazy... I just have Fasterfox, Tab Mix Plus, and the tango icon theme installed.

I've actually decided to ditch Beryl for now, too. For the most part it worked well, but my computer doesn't have the horsepower to deliver a constantly smooth experience. Plus, it didn't handle window focus well, using the Window Picker/Expose thing to switch between windows on different viewports doesn't always switch focus, which kinda defeats the purpose. I took a step back and realized that I'm using software at revision 0.2. That's pretty damn beta.

Anyway, I'm going to see if dropping Beryl has any effect. We'll see.

 

Yeah, Beryl's a crapper. Not worth it at all, IMO.

 

I have also been giving Beryl a rest lately. If you have any time of GL desktop enabled with the nvidia-glx drivers, you apparently lose the suspend/hibernate functions on your laptop. Those are my most used functions, so I just can't deal with that. And to be honest, neither Compiz nor Beryl are stable enough to rival Aero, so it gets a no-go in my book.

 

I haven't ever gotten my notebook to properly suspend or hibernate when the nvidia-glx drivers are installed... it always whites out the screen when hibernating, and does the same when it resumes. Kinda scary, because it usually means that it's feeding random high voltages to the LCD. So I just start it up and shut it down. It doesn't take that much more time, and is much more functional, at least on my hardware.

 

FF has always been a cpu hog. Try downloading something and have multiple browsers open

 

Going back to BigV's original comment about FF2.0 eating a big one, has anyone tried SwiftFox? Is it superior to FF2.0 with respect with memory consumption? Can it use all of FF2.0's extensions (AdBlock, Fasterfox)?

 

My notebook does that when going to hibernate with the 97.55 drivers. Ubuntu actually updated last night and downgraded the drivers back to 96.something, and I haven't tried it again yet. But I don't have any problems with suspend right now. It looks a little funny, and if I have my mouse plugged in, it will give some weird text about reinitializing the USB hub or something before it wakes back up. But it's mainly what I use. I didn't know that the white-out thing was high voltages going to the LCD... don't think I'll be using hibernate too much anymore. Like I said, I'm more of a suspend person anyhow.

 

swiftfox is just firefox compiled for a specific architechture.

I don't use it because the guy who distributes it changed the license to a non-free one.

 

Well, the source code is still available, it's just the binaries that are "non-free." Still, it's non-free and not redistributable, so I'll steer clear of it as well. I can see why he did it, but it doesn't make it right.

 

I too am in the same boat... I've also decided to ditch Beryl for a while. Although 0.2 was a big step in the right direction in terms of stability... I agree that my computer just doesn't have the horsepower to make it a totally awesome experience. Everything just feels so much snappier without Beryl running...

As for FF2 crashing... it doesn't really crash for me. The only time it crashes (consistently) is when I'm trying to watch streaming videos that are in wmv format (i.e. using the totem plugin). Other than that, FF2 has been pretty stable...

 

Dang... I must be the only one that likes Beryl... hehe. The only problem is that it does crash it a lot. But since they've updated things lately, I'll have to check out and see if things have stabilized with the different nvidia-glx drivers. I'm on a business trip, so I don't have my personal laptop with me. I'll do it this weekend or something

 

lol... I like it, it's just that there are a few problems that need to be corrected for things to be "hunky dory"

 

@Pita - I think you are just more patient than the rest of us when it comes to getting Beryl to run properly. It's a virtue

 

stupid thing did it again...

I took a screenie. The thing only crashes when you actually close one of these freaky windows...

I had multiple tabs open in the main window, opened another one to check here, typed in the URL/autocompleted, I clicked the "quick link" to the most recent post for the Linux forum... then the one window that covers most of the screen comes up with the actual website, and then that other little one looks like it has the google ads...

 

You're going to wanna watch that last update. They renamed the current nvidia-glx drivers (97.55) to nvidia-glx-new, and so the latest Fesity update actually downgrades your drivers to 96.31. The problem is that this kills your X. It only replaces the actual drivers and fixes your xorg.conf file, but that doesn't do anything about the nvidia kernel (which is still seeing 97.55). Therefore, upon first boot, you'll get a broken X due to conflicting APIs. Here is a thread that should help you avoid all the hassle. You can see what I had to go through (my handle is also notebook_ftw there).

 

I'm also running Linux pretty much exclusively, and I'm very comfortable with the command line and other stuff, so it's not nearly as big of a deal if my graphics and such take a dive I've built an xorg.conf by hand from the ground up before.

Thanks for the link notebook_ftw... I'll keep that in mind.

 

LOL! I wasn't thinking about command line skills...I think many of us here have that...I mean being patient with Beryl crashing and freezing X!