User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1b2) Gecko/20060821 Firefox/2.0b2 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1b2) Gecko/20060821 Firefox/2.0b2 I was using the forums and I had multiple tabs open. usually I can refresh with no problem but once in a while, the browser would just crash (usually crashed 9-12 times a day) Reproducible: Sometimes Steps to Reproduce: 1.use forums or any other site 2.browse around and refresh a few pages 3.will sometimes crash. Actual Results: Firefox will crash and would ask me if i want to report the error sometimes when Firefox crashes, all of my settings will be set to default from my custom settings and i will have to set Firefox back to my default browser and re set everything up again. Expected Results: What should the software have done instead? well it should have not crashed. other browsers don't do this bug id TB23082652G sometimes firefox would just close randomly and the talkback will not even show up but the windows xp built in error reporter will come up PS i am using firefox 2
That stack is bogus, can you try crashing again and getting another Talkback ID?
(In reply to comment #1) > That stack is bogus, can you try crashing again and getting another Talkback > ID? > ill try, may take some time as this is completely random how the browser crashes
(In reply to comment #1) > That stack is bogus, can you try crashing again and getting another Talkback > ID? > It crashed again while i was reading a article bug id TB23163725X
Are you using any extensions? Incident ID: 23163725 Stack Signature TimerThread::AddTimerInternal e6669ff3 Product ID Firefox2 Build ID 2006082101 Trigger Time 2006-09-11 12:00:34.0 Platform Win32 Operating System Windows NT 5.1 build 2600 Module xpcom_core.dll + (00031290) URL visited User Comments war reading a article at techgage.com then all of a suddon while going to the next page, firefox crashed Since Last Crash 44999 sec Total Uptime 50448 sec Trigger Reason Access violation Source File, Line No. c:/builds/tinderbox/Fx-Mozilla1.8-release/WINNT_5.2_Depend/mozilla/xpcom/threads/TimerThread.cpp, line 400 Stack Trace TimerThread::AddTimerInternal [mozilla/xpcom/threads/TimerThread.cpp, line 400] TimerThread::AddTimer [mozilla/xpcom/threads/TimerThread.cpp, line 331] nsAppStartup::Run [mozilla/toolkit/components/startup/src/nsAppStartup.cpp, line 152] main [mozilla/browser/app/nsBrowserApp.cpp, line 61] kernel32.dll + 0x16fd7 (0x7c816fd7)
Component: General → XPCOM
Product: Firefox → Core
QA Contact: general → xpcom
Summary: crashed when refreshing pages → crashed when refreshing pages [@ TimerThread::AddTimerInternal]
Version: unspecified → 1.8 Branch
yep I am using adblock plus, inline auto complete and down them all
There are 557 other crashes with such a stack signature: http://talkback-public.mozilla.org/search/start.jsp?search=1&searchby=stacksig&match=contains&searchfor=+TimerThread%3A%3AAddTimerInternal&vendor=MozillaOrg&product=All&platform=All&sortby=bbid&rlimit=0 It seems to happen for all platforms, Firefox and Thunderbird and different branches (1.8.0 and 1.8).
Status: UNCONFIRMED → NEW
Ever confirmed: true
crashes are beginning to become more frequent not sure if these are needed anymore since others are also having this problem. TB23329411Q, TB23297356E, TB23286236X, TB23257255H, TB23253392X, TB23247173E, TB23245911Q
inuyasha6332, only a few of those crashes were the same as the crash this bug is about. We really don't need anymore Talkback IDs, really. What would help here is if you could determine if one of your extensions is causing this. Do you see the crash with DownThemAll disabled? With both DownThemAll and Adblock disabled? With Inline Autocomplete disabled, etc.?
Since the page is gone and the stacks are very short, I'm marking this bug as incomplete. If you're still seeing crashes, please file new bugs (with IDs from about:crashes).
Status: NEW → RESOLVED
Last Resolved: 9 years ago
Resolution: --- → INCOMPLETE
Crash Signature: [@ TimerThread::AddTimerInternal]
You need to log in before you can comment on or make changes to this bug.