User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:184.108.40.206) Gecko/20061204 Firefox/220.127.116.11 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9a1) Gecko/20061006 Sunbird/0.3 Sunbird always crashes after exactly 10 minutes (to the second) even when if it's not being used. Reproducible: Always Steps to Reproduce: 1. Launch Sunbird 2. Wait for 10 minutes Actual Results: It crashed with a Windows "Send error report" message. Expected Results: well... not crashing? I don't use Sunbird very heavily. I have less than 20 events in my calendar and only have the "Talkback" add-on (v0.3) installed.
Your bug report doesn't contain enough information to analyze the problem, e.g. if there are any error messages shown. Therefore I can only guess that this is the same issue as in Bug 357106 that is a duplicate of Bug 331404. Can you run the findold tool [https://bugzilla.mozilla.org/attachment.cgi?id=224295] that is attached in Bug 331404 and see if it lists files?
Yes it lists a very old file (from 1617) so it might be the same bug. However the crash still happens even after having changed the date of the file. There's no error message - just the standard Windows "Send an error report" message box. This is what I get in the Event Viewer: "Faulting application sunbird.exe, version 0.3.0.0, faulting module msvcr80.dll, version 8.0.50727.163, fault address 0x000177a9." I don't know if it's related but this event also always appear a few seconds after the sunbird crash: Event Type: Error Event Source: Application Error Description: Fault bucket 335088323.
Laurent, please check http://forums.mozillazine.org/viewtopic.php?t=511815 The user had the same issue, maybe you can follow the more detailed workaround description posted there.
Thanks Stefan, I moved the old file to a different folder and it solved the problem. I guess the bugs could be tagged as a duplicate of 331404.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 11 years ago
Resolution: --- → DUPLICATE
Duplicate of bug: 331404
You need to log in before you can comment on or make changes to this bug.