crashing by TB unresponsive script, all TB tasbs became unresponsive, not accessible, although emails were received, but could not read
I tackled this problem above mentioned myself, after trial & error, during several days I removed TB 52.2.1 NL completely. Then I installed TB 52.2.1 US-en, This was my way of overcoming the problem, finally.
In case this turns up again in future , what else can I do, to solve more effectively and easily?
I'm already using TB for more than 15 yrs, with satisfaction in general.
Wybrane rozwiązanie
As far as I know, there are no known issues for localized versions to cause problems where en-US versions don’t (in 52.x).
Did you also create a new profile when reinstalling? If so, that may be a more obvious reason the issue did not return. If you did not, the uninstall and reinstall itself would have been the solution rather than the language version. That means you could safely uninstall the en-US version now and install the Dutch version again.
As for unresponsive behavior, the fastest way to tackle is, and you may know, to launch Thunderbird (or Firefox) with another profile, or just to keep that profile for testing purposes like these. A second profile indicates whether an issue is profile related, varying between corrupt files, modified settings and (usually) add-ons causing troubles.
For add-ons, Thunderbird’s Safe Mode quickly disables any add-ons and themes in a test mode. Unfortunately a number of Thunderbird add-ons are no longer updated by their developers while they remain enabled, but unlike Firefox, they are neither detected as outdated nor blocked simply because the developer assumes they still work.
You could also clean the cache part of a profile - not the profile itself - meaning the profile path with Local instead of Roaming in it. I also believe some users reported cleaning Windows Temp files helped them, though they were more related to startup issues.
Does this answer your question? I’d be happy to hear what happens if you reinstall the Dutch version. You could even install an older Dutch version if you think it is language and version related.
Przeczytaj tę odpowiedź w całym kontekście 👍 0Wszystkie odpowiedzi (3)
Wybrane rozwiązanie
As far as I know, there are no known issues for localized versions to cause problems where en-US versions don’t (in 52.x).
Did you also create a new profile when reinstalling? If so, that may be a more obvious reason the issue did not return. If you did not, the uninstall and reinstall itself would have been the solution rather than the language version. That means you could safely uninstall the en-US version now and install the Dutch version again.
As for unresponsive behavior, the fastest way to tackle is, and you may know, to launch Thunderbird (or Firefox) with another profile, or just to keep that profile for testing purposes like these. A second profile indicates whether an issue is profile related, varying between corrupt files, modified settings and (usually) add-ons causing troubles.
For add-ons, Thunderbird’s Safe Mode quickly disables any add-ons and themes in a test mode. Unfortunately a number of Thunderbird add-ons are no longer updated by their developers while they remain enabled, but unlike Firefox, they are neither detected as outdated nor blocked simply because the developer assumes they still work.
You could also clean the cache part of a profile - not the profile itself - meaning the profile path with Local instead of Roaming in it. I also believe some users reported cleaning Windows Temp files helped them, though they were more related to startup issues.
Does this answer your question? I’d be happy to hear what happens if you reinstall the Dutch version. You could even install an older Dutch version if you think it is language and version related.
It is solved , I didn't change my profile, and now it's OK again with Dutch version 52.2.1.
Would Beta 55.0 be a ( better?) idea?
eendnust said
It is solved , I didn't change my profile, and now it's OK again with Dutch version 52.2.1. Would Beta 55.0 be a ( better?) idea?
We don't know what caused this, so beta not necessarily better.
Please update this post when 52.3.0 comes out in 1-2 weeks.