User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0; Avant Browser; Avant Browser) Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8.1a3) Gecko/20060602 BonEcho/2.0a3 After having Firefox open awhile, when I close it, it crashes after the window disappears and when I restart it, it becomes very unstable. For instance, some links will cause it to crash, or attempting to go to some websites in the URL such as "bugzilla.mozilla.org" will also make it crash. When I restart my comp, everything works again, for awhile. Reproducible: Always Steps to Reproduce: 1.Keep Firefox open awhile 2.Close it an it crashes. 3.Reopen it and it becomes very unstable Actual Results: It crashes. Expected Results: It should not crash. I've tried this in a fresh profile without doing anything more than removing the bookmarks toolbar.

The attachment is a Dr. Watson log reported by windows when Firefox crashed initially. It also contains the subsequent crash logs it causes when trying to restart the program and browse.

I'd also like to add that after the initial crash, it will also crash while trying to download plugins in the plugin manager as well as the updater and it will of course continue to crash on exit as well.

Comment on attachment 224296 [details] This is the log that Dr Watson reported. i'm sorry, this is useless. you can either: 1. install a talkback enabled build 2. install a build for which we offer a symbol server + a debugger and follow the instructions to get a useful stack 3. install a build environment and build yourself note that i'll gladly analyze just about any stack imaginable, including bluescreen crashes on windows and i just spent hours on linux crashes. drwatson reports just aren't useful unless all symbols are in fixed locations, and random builds just don't fit that profile.

I couldn't locate a talkback build for 2.0a3. Sorry, I can't help much.

from your dr. watson tasklist you're running 'AdMunch.exe' see bug 342646 for this issue. to OP, will deactivating admuncher or starting it _after_ an initial http request from FF resolve your issues ?

You know, you asking me that question made a lightbulb turn on in my head. I haven't had crashes in a long time with FF and I realized that I haven't been running admuncher in quite awhile. So after I read this, I booted up admuncher and let it run with FF for awhile and sure enough, after about an hour of usage, FF crashed. Sooo, I bet that's probably what's causing it.

*** This bug has been marked as a duplicate of 342646 ***