We're calling on all EU-based Mozillians with iOS or iPadOS devices to help us monitor Apple’s new browser choice screens. Join the effort to hold Big Tech to account!

Avatar for Username

Rechercher dans l’assistance

Évitez les escroqueries à l’assistance. Nous ne vous demanderons jamais d’appeler ou d’envoyer un SMS à un numéro de téléphone ou de partager des informations personnelles. Veuillez signaler toute activité suspecte en utilisant l’option « Signaler un abus ».

En savoir plus

Ce sujet de discussion a été archivé. Veuillez poser une nouvelle question si vous avez besoin d’aide.

Thunderbird hangs on exit

  • 4 réponses
  • 1 a ce problème
  • 13 vues
  • Dernière réponse par fuffberry

fuffberry
fuffberry
more options

Linux 64 version in all cases (TB 37 and TB68.9) Upon exit, the thunderbird task remains an active process for somewhere between 1 and 5 minutes. This always happens if messages are deleted added (downloaded) or the mailboxes are compressed. Bringing up TB, finding no new messages and selecting quit (File->Quit) sometimes does close the thunderbird process. The work around is to manually kill the thunderbird process.

Linux 64 version in all cases (TB 37 and TB68.9) Upon exit, the thunderbird task remains an active process for somewhere between 1 and 5 minutes. This always happens if messages are deleted added (downloaded) or the mailboxes are compressed. Bringing up TB, finding no new messages and selecting quit (File->Quit) sometimes does close the thunderbird process. The work around is to manually kill the thunderbird process.

Toutes les réponses (4)

Wayne Mery
Wayne Mery
  • Moderator
  • Top 10 Contributor
more options

So if you do not do the compact function, then shutdown works fine?

fuffberry
fuffberry Auteur de la question
more options

While the compact function will result in the task hanging result, it is not the only way to cause it. Receiving email also result in the hanging task. It's as things which alter the messages such as compression or receiving more messages also results in the hanging situation. If a TB session is used only to view existing messages (no additions, deletions, movement or compression) there won't be a hang.

Matt
Matt
  • Moderator
  • Top 10 Contributor
more options

I am sorry, but the existence of task is not really proof of anything, except that there is no GUI loaded. The task hanging around could have a number of legitimate reasons, not the least of which is indexing of messages to the global index. I see even with a GUI that sometime this can take 5 or 10 minutes per account. The activity manger will report "determining which messages to index" for quite lengthy periods at times.

fuffberry
fuffberry Auteur de la question
more options

Thunderbird hangs for awhile. Eventually it crashes after displaying some lines if you invoked it through a command line (and yes, the command thunderbird -p xxx does bring up the GUI). Those behind the scene lines are: WARNING: A completion condition encountered an error while we were spinning the event loop. Condition: Telemetry: shutting down Phase: profile-before-change2 State: (none) WARNING: [Exception... "Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIObserverService.removeObserver]" nsresult: "0x80004005 (NS_ERROR_FAILURE)" location: "JS frame :: resource://gre/modules/TelemetryPing.jsm :: detachObservers :: line 970" data: no] WARNING: detachObservers@resource://gre/modules/TelemetryPing.jsm:970:4 uninstall@resource://gre/modules/TelemetryPing.jsm:1170:4 Impl.shutdown@resource://gre/modules/TelemetryPing.jsm:1297:4 condition@resource://gre/modules/TelemetryPing.jsm:1037:15 Barrier.prototype<._wait@resource://gre/modules/AsyncShutdown.jsm:648:26 Barrier.prototype<.wait@resource://gre/modules/AsyncShutdown.jsm:614:27 Spinner.prototype.observe@resource://gre/modules/AsyncShutdown.jsm:356:18

Segmentation fault (core dumped)