Przeszukaj pomoc

Unikaj oszustw związanych z pomocą.Nigdy nie będziemy prosić Cię o dzwonienie na numer telefonu, wysyłanie SMS-ów ani o udostępnianie danych osobowych. Zgłoś podejrzaną aktywność, korzystając z opcji „Zgłoś nadużycie”.

Więcej informacji

102 Crashes [@ OOM | small ] every day on Windows, but not on Mac

  • 15 odpowiedzi
  • 0 osób ma ten problem
  • 2 wyświetlenia
  • Ostatnia odpowiedź od Wayne Mery

more options

Every day my Thunderbird crashed when getting email. I assumed it was a corrupt email rule, annoying but not sure how to address. Incidentally a few months ago, due to another project, I had to move my Thunderbird profile from my Windows machine to my Mac and when I did the crashing stopped. That project has now finished and I've moved my profile back to my Windows machine and the problem is back. I've installed the latest 102.13.0(64 bit) version of Thunderbird, but no difference. Are there any logs that might show in a bit more detail what's going on ? The log that's shown with the "Thunderbird has crashed" message seems to be little use.

Any other suggestions as to why the mac is happy but Windows isn't ?

Cheers

David

Every day my Thunderbird crashed when getting email. I assumed it was a corrupt email rule, annoying but not sure how to address. Incidentally a few months ago, due to another project, I had to move my Thunderbird profile from my Windows machine to my Mac and when I did the crashing stopped. That project has now finished and I've moved my profile back to my Windows machine and the problem is back. I've installed the latest 102.13.0(64 bit) version of Thunderbird, but no difference. Are there any logs that might show in a bit more detail what's going on ? The log that's shown with the "Thunderbird has crashed" message seems to be little use. Any other suggestions as to why the mac is happy but Windows isn't ? Cheers David

Zmodyfikowany przez Wayne Mery w dniu

Wybrane rozwiązanie

I have solved the problem by increasing the amount of memory available in my (virtual) machine.

I'm assuming that there's some code somewhere that doesn't respond correctly to a lack of memory situation, maybe requesting memory and not responding gracefully to an inability for that memory to be supplied.

Przeczytaj tę odpowiedź w całym kontekście 👍 0

Wszystkie odpowiedzi (15)

more options

What are the crash Id's? https://support.mozilla.org/en-US/kb/mozilla-crash-reporter-tb#w_viewing-crash-reports

With the Id's we can actually look at the uploaded crash data and make more informed suggestions.

more options

Matt two from earlier this week

bp-b3e32c43-f6b6-4eb2-825a-794510230714 bp-432077dd-2b71-4c41-bd04-ae08d0230713

What's odd is they seems to be Out of memory errors but I can see the Virtual memory is reporting ridiculous values for virtual memory e.g. 150 TB, so is there some underlying memory manager issue ?

As Thunderbird is running in a VM (it's all that is running BTW) I can change the amount of memory the machine has if this is a genuine out of memory error, but it's odd that it only occurs once every 24 hours.

David

Zmodyfikowany przez dsr2 w dniu

more options

You have several add-ons installed. Please disable them all. Does the crashing stop?

If it does not stop, what happens if you start Thunderbird in troubleshoot mode? https://support.mozilla.org/en-US/kb/troubleshoot-mode-thunderbird

more options

It would be interesting to know if you have the backup part of the import export tools enabled as that is one of the things that would kick off once a day. IS is also a JavaScript that runs in a recursive manner so could easily run into memory issues. This would be especially so if there are physical errors in some of the store files on disk.

more options

Extensions disabled and no crash so far this morning.

Addons I have are

Addon Compatibility Check Folder Account ImportExportTools NG LookOut (fix version) Provider for Google Calendar Quick Folder Move Signature Switch

I'm guessing the best thing to do is to leave it another 48 hours to be sure it's not going to crash and then enable the extensions one by one, a day at a time, until it does crash ?

more options

Definitely give it a couple more days and then let us know the results.

more options

Crashed again this afternoon (I wasn't in work this morning) with all my addons disabled.

https://crash-stats.mozilla.org/report/index/6bb9a54e-aaaa-4f64-baf0-bcf300230717

What's the next step please ?

more options

Try Help > Troubleshoot mode please.

more options

Been running in Troubleshoot mode for 2 days now and no crashes. :) So whilst this is good, what do I do now to safely return to none Troubleshoot mode please ?

more options

Matt said

It would be interesting to know if you have the backup part of the import export tools enabled as that is one of the things that would kick off once a day. IS is also a JavaScript that runs in a recursive manner so could easily run into memory issues. This would be especially so if there are physical errors in some of the store files on disk.

dsr2 said

Been running in Troubleshoot mode for 2 days now and no crashes. :) So whilst this is good, what do I do now to safely return to none Troubleshoot mode please ?

Do you have the backups enabled in the import export tools add-on you have installed?

more options

Sorry about the delay in replying

> Do you have the backups enabled in the import export tools add-on you have installed?

No. I've also checked all the other addon, and none seem to have any periodic function.

more options

Just crashed again and I was sure I was in troubleshooting mode at the time.

https://crash-stats.mozilla.org/report/index/dd4a7217-edf6-48f3-b53f-a27c60230724#tab-details

more options

This is getting worse. Now crashing several times a day. This morning the error wasn't even captured by the Thunderbird normal error handler.

more options

Wybrane rozwiązanie

I have solved the problem by increasing the amount of memory available in my (virtual) machine.

I'm assuming that there's some code somewhere that doesn't respond correctly to a lack of memory situation, maybe requesting memory and not responding gracefully to an inability for that memory to be supplied.

more options

You had less than 400mb allocated to the VM?