Closed Bug 256795 Opened 20 years ago Closed 19 years ago

Crash often since XP SP2 install [@ destroyTimerEvent ]

Categories

(Firefox :: General, defect)

x86
Windows XP
defect
Not set
critical

Tracking

()

RESOLVED EXPIRED

People

(Reporter: postmaster, Assigned: bugzilla)

Details

(Keywords: crash)

Crash Data

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7) Gecko/20040626 Firefox/0.9.1 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7) Gecko/20040626 Firefox/0.9.1 Since I installed WIndows XP Service Pack 2 I observe crash of the browser (3 in 4 days) whereas nothing else changed on my computer and the rate before was more something like once in several weeks... Unfortunately only one crash triggered talkback, the other triggered the Microsoft crash reporting stuff. I guess this bug report won't help to much, but it is the best I can do right now - I'll add talkback incident as sson as I can get more. Reproducible: Couldn't Reproduce Steps to Reproduce: 1. 2. 3.
franCk: Please provide TalkBack incident ID as soon as will be available.
Severity: normal → critical
Keywords: crash
TB637773K It was the one that trigered the talkback - the other 2 corresponded more exactly to application hang (for > 20min) and I had to kill them which prompted a crash report from Microsoft (but no talkback) I will add more to this bug when they happen to see if there is any common point between them. [BTW, note that the admin in my Uni have just recommended to not install SP2 yet, pending further tests - maybe it cause some incompatibility with some of our network...]
TB637773K: destroyTimerEvent [c:/builds/tinderbox/firefox-0.9.1/WINNT_5.0_Clobber/mozilla/xpcom/threads/nsTimerImpl.cpp, line 455] 0x778b0c24 morkObject::`scalar deleting destructor' 0x00ffffb8 NS_NewGenericModule2 [c:/builds/tinderbox/firefox-0.9.1/WINNT_5.0_Clobber/mozilla/xpcom/glue/nsGenericFactory.cpp, line 511] 0x088b0674
Summary: Crash often since XP SP2 install → Crash often since XP SP2 install [@ destroyTimerEvent ]
OK, after a few more weeks I do not have crashes anymore, thus it may just have been purely coincidental - most probably no link with SP2 install and just some 'normal' rarely triggered crash that just happened to occur in a row... Note that since then I've upgraded to Firefox PR. I won't close the bug because I really had a crash, and it may turn up in other trackback incident, but from my side it seems to have no relationship with SP2 install, thus I'm tempted to remove that from the summary, it could be misleading... Should I do that?
(In reply to comment #4) I have still the Problem you discribed. I'm not a Programmer but i think it depends on Scripts or Appelets on Page. For Example a crash for sure ist the Real-Time-Pushlist vom http://www.ariva.de, but it crashed in ebay also. THX Christian Meier
This is an automated message, with ID "auto-resolve01". This bug has had no comments for a long time. Statistically, we have found that bug reports that have not been confirmed by a second user after three months are highly unlikely to be the source of a fix to the code. While your input is very important to us, our resources are limited and so we are asking for your help in focussing our efforts. If you can still reproduce this problem in the latest version of the product (see below for how to obtain a copy) or, for feature requests, if it's not present in the latest version and you still believe we should implement it, please visit the URL of this bug (given at the top of this mail) and add a comment to that effect, giving more reproduction information if you have it. If it is not a problem any longer, you need take no action. If this bug is not changed in any way in the next two weeks, it will be automatically resolved. Thank you for your help in this matter. The latest beta releases can be obtained from: Firefox: http://www.mozilla.org/projects/firefox/ Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html Seamonkey: http://www.mozilla.org/projects/seamonkey/
This bug has been automatically resolved after a period of inactivity (see above comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → EXPIRED
Crash Signature: [@ destroyTimerEvent ]
You need to log in before you can comment on or make changes to this bug.