Ce site disposera de fonctionnalités limitées pendant que nous effectuons des opérations de maintenance en vue de vous proposer un meilleur service. Si un article ne règle pas votre problème et que vous souhaitez poser une question, notre communauté d’assistance est prête à vous répondre via @FirefoxSupport sur Twitter, et /r/firefox sur Reddit.

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

crash after creators update @ RefPtr<T>::assign_with_AddRef | mozilla::GenericFactory::CreateInstance

  • 11 réponses
  • 2 ont ce problème
  • 7 vues
  • Dernière réponse par Zoll

more options

after the windows 10 creators update I have used my laptop during an afternoon running thunderbird last version 52.1.1 then there was a crash with a complex crash report which i've forwarded to thunderbird. are there other cases of crashes of thunderbird after creators update? before i've never had a thunderbird crash

after the windows 10 creators update I have used my laptop during an afternoon running thunderbird last version 52.1.1 then there was a crash with a complex crash report which i've forwarded to thunderbird. are there other cases of crashes of thunderbird after creators update? before i've never had a thunderbird crash

Modifié le par Wayne Mery

Toutes les réponses (11)

more options
more options
more options

bp-fbf4957d-1e6b-4981-9c3a-129f20170516 bp-4baeed17-125e-43a2-82fb-e41260170516 both have same crash signature.

What are you doing when you crash - are you sending an email? Do you have the "send later" addon installed?

more options

I believe i was surfing, i was doing nothing with thunderbird or the only thing i could be doing was reading email (imap). the only add-ons i have is: importexport tools lightning

more options

Maybe the crash has to do with the installation of the new version 52.1.1 because I see this version has been installed on 17/05/2017 : the same day as the crash.

more options

Sorry I was wrong the crash was on 16/05/2017 and the new version was on 17/05/2017

more options

I have this problem as well and sending repeated crash reports to Mozilla. The program crashes at random intervals of 10-40 minutes after opening- often when idle. Updated to Windows 10, version 1703 Creators Update on 04 June 2017. - Any help would be really appreciated.

bp-d274b259-43d7-4773-b5e4-e23d30170608

more options

Zoll said

I have this problem as well and sending repeated crash reports to Mozilla. The program crashes at random intervals of 10-40 minutes after opening- often when idle. Updated to Windows 10, version 1703 Creators Update on 04 June 2017. - Any help would be really appreciated. bp-d274b259-43d7-4773-b5e4-e23d30170608

@[Zoll] If the above information does not resolve your issue, please consider creating a new thread containing the specific details of your issue.

Doing so will allow the Mozilla volunteers to give you solutions that are more helpful to you. This may help them to solve your problem faster and more efficiently.

Please, feel free to post the link to your thread on this thread for volunteers interested in assisting you.

However I strongly recommend you try the following before posting a new thread. You have the bitdefender add-on installed and it may well be the problem.

Restart Thunderbird with add-ons disabled (Thunderbird Safe Mode). On the Help menu, click on "Restart with Add-ons Disabled". If Thunderbird works like normal, there is an Add-on or Theme interfering with normal operations. You will need to re-enable add-ons one at a time until you locate the offender.

more options

@[Matt] Thanks- Will try disabling the add ons and see where it takes me.

more options

Hey Zoll. What were you able to find?

more options

Wayne Mery said

Hey Zoll. What were you able to find?

I have disabled the bitdefender and add-signature add on as @Matt recommended above, and it appears to have solved the problem so far.......... Will keep you posted