Comment 6 for bug 582640

No, i didn't have too many tabs open, only two lines of text, one said
Window, and under the window was the content, forget what, but most likely
Google. So the box wasn't expanded downwards at all. The box was practically
empty. So there wouldn't be a bad tab, i also used it until i realized it
just keeps crashing, and did and used different things and loaded different
websites.
I forgot to mention too, after the reboot, the firefox would be starting on
it's own, even tho it's not in the startup menu.
Last night, i walked away from it for an hour or so, and the screen was
black, it was in terminal mode, but not the virtual terminal in GNOME, but
the kind that comes up when booted in maintenance mode. And it was scrolling
through different processes, and it went on and on, and killing the
processes, i wish i could have captured it, but it was scrolling so i didn't
even know how many screens have already scrolled past, and if it was
looping. Then it stopped and asked for log-in, but it didn't accept the
log-in and started working away feverishly again. This happend only once, so
far.
It was caused by too many tabs and too much content, i read BBC News website
every day, and it's full of graphics and videos, and it froze up on me a few
times, but it never crashed to have to reboot it.
The Force Quit doesn't help either, the firefox comes back to haunt me, like
Mc Donald's hamburger.

On Fri, May 21, 2010 at 12:16 PM, madbiologist <email address hidden> wrote:

> If I'm understanding you correctly, you need to scroll down to the
> buttons on the Restore screen because you had a _lot_ of tabs open?
> Maybe too many for 512 Mb RAM? When RAM is full your swap partition
> should be used but if that gets full too then you might have a
> (crashing) problem. What does the Resources tab of System Monitor (under
> System -> Administration) show? Or it could be that one of the tabs has
> a page with a bad piece of Javascript, causing Firefox to crash.
>
> To get out of the Restore cycle you describe, as soon as you have
> successfully restored a browsing session, close Firefox before it
> crashes again. You will be asked if you want to save all your open
> tabs, I recommend saying "no", but even saying "yes" should result in
> your next Firefox launch working better than an automatic restore,
> although it might crash again after that depending on number of tabs
> open and/or a bad piece of Javascript on a page in one particular tab.
>
> --
> firefox 3.5 crashes
> https://bugs.launchpad.net/bugs/582640
> You received this bug notification because you are a direct subscriber
> of the bug.
>