[RESOLVED] Forum Crashes Firefox

shu

When trying to submit a reply, this forum frequently crashes my Firefox browser, taking along with it the replies I just typed up. I am just curious if it's just me or someone else experience this issue as well?

bpat1434

Moving to a more appropriate forum ...

And I've only ever had timeouts, never Firefox crashes.

sheephat

It may be your computer is running a high amount of process or your RAM has filled up quickly. Sometime firefox has been known to steal alot of your RAM memory, and when it does would either make parts disappear or close altogether.

There is also the posibility that the adverts on the site are causing it.

shu

Normal browsing is no problem, it crashes the browser when I click on any of the button to submit a reply. It's kinda of wierd...

sheephat

Hmmm, is it the most update version of firefox?

shu

Yeah, 2.0.0.4! It crashed four times today so far 🙁

sheephat

I think all the problems I had with firefox, are what lead me back to internet explorer.

To be honest I only use firefox to open pages IE cannot, so im not familiar with firefox, maybe it has something to do with your computers setup / specifications.

stolzyboy

this won't fix the problem... but with forums, i've taken to copying what i've typed(if it's long) before i submit just for reasons of timeouts/etc...

just a simple workaround 🙂

sheephat

The best method is to type them into a word processor, that way they are spell checked and punctuated.

Also if they get timed out then there is a copy of it like you said.

Of course if it is a short post it’s not necessary.

MarkR

Do the following:

Disable all plugins and third party add-ons - you can do this from the menus and/or by some setting in about:config
Try again. If that doesn't fix it, also erase your profile.
If it still crashes, try a reinstall
If, after a reinstall, with no third party plugins or addons, it still crashes, you MUST file a bug report on Bugzilla.

The only way software can improve is if people report bugs!

By the way, it is highly likely that a third party plugin (especially Flash) is crashing it, not the Mozilla browser itself. The problem is, that many plugins frequently issue updated which break Mozilla; this is not Mozilla's fault.

Mark

stolzyboy

sheephat wrote:
The best method is to type them into a word processor, that way they are spell checked and punctuated.

Also if they get timed out then there is a copy of it like you said.

Of course if it is a short post it’s not necessary.

i'm typing on a forum... i could care less if i spelled everything correctly...

sheephat

The main reason that I do it that way is because I used to be the administrator for a political forum, and it was best that most to all my posts were of the highest quality in terms of spelling and punctuation.

However on this forum I make less of an effort, and besides notepad loads faster than Word.

Weedpacket

MarkR wrote:
1. Disable all plugins and third party add-ons - you can do this from the menus and/or by some setting in about:config

There should also be an option to start in Safe Mode that has the same effect.

sheephat wrote:
it was best that most to all my posts were of the highest quality in terms of spelling and punctuation.

Firefox has spellcheck built in, and I've found that Word's grammar check (for punctuation and such) is utter rubbish.

cahva

PHPBuilder crashed on me too but I found that the reason was in Firebug extension. Now when I have disabled it in phpbuilder, I've had no crashes since.

shu

cahva wrote:
PHPBuilder crashed on me too but I found that the reason was in Firebug extension. Now when I have disabled it in phpbuilder, I've had no crashes since.

I do too have the Firebug extension installed. I just disabled it, and going to leave it disabled for while see if it solve my problem here on the forum. Thanks!

shu

With Firebug disabled, no more crashes! Looks like it's the culprit!! hooray...

Weedpacket

Sounds like a bug report to Firebug's author(s) would be in order at this point. It sounds like something about how it monitors Javascript execution is broken.