…yeah, this’ll be boring.

I’ve had a hell of a time keeping Firefox stable ever since 3.5 came out. Of course, I’ve not been one to try to give up any of my extensions, even though the probable cause of the crashes would be an add-in that doesn’t play well with 3.5 despite claims that it does.

So my add-ins were as follows:
Tab Mix Plus
Delicious Bookmarks
NoScript
AdBlock Plus
Greasemonkey
XMarks
Stylish
All in One Sidebar

Now, honestly, I tried everything short of the proper way of doing this. The PROPER way to troubleshoot is a fresh profile, install 1 addon at a time, and if it doesn’t crash the browser try the next one. Me? Nah, I’d play til it crashed, disable one, and try again. It wasn’t working. I had them all disabled at one point, and it was still crashing. This went on for 3 weeks.

Fine.

So we started Monday with a fresh profile and no addins. Play for a day, no problems. Tuesday’s child was NoScript. Go for a day, no problems. That’s a good sign…
Wednesday (today) was AdBlock Plus. I didn’t expect a problem with it, and indeed haven’t heard of any. I installed it early this morning, then went to work. When I came home, though, the first thing that happened when I loaded Firefox was a crash. Huh, how ’bout that. I uninstalled AdBlock Plus and installed Greasemonkey. Then THAT crashed.

WTF?

OK, interesting. I’ve got that set aside, if I can get the rest of the extensions working I’ll go back and play with those two.

In the meantime, we’re working on Tab Mix Plus. This is one of just a couple that I have determined that I shouldn’t be able to live without… XMarks being the other. If I can’t get them going, I’m going to throw in the towel and go on to Google Chrome. If Greasemonkey is truly failing me I might be inconsolable, as well, but that’s only for the Arstechnica.com LastReadPost script, but anyway.

The moral of this story is to do things the right way, the first time, and save yourself a few weeks of wailing and gnashing of teeth.