Re: following thunderbird upgrade to 102, it takes over 1h of 100% CPU to start

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 28/8/22 18:25, Eyal Lebedinsky wrote:
f36, just updated and received thunderbird-librnp-rnp-102.2.0-1.fc36.x86_64
from thunderbird-91.12.0-1.fc36.x86_64

tb brings up the expected display but no input is accepted. The process is shown as running with 100% CPU         PID USER      PR  NI    VIRT    RES    SHR S  %CPU %MEM     TIME+ COMMAND       72149 eyal      20   0 4075036 772700 223612 R 100.3   2.4 5:26.57 thunderbird It will not refresh(*) the panel and will start responding after about 1h.
    [later] I see the panel was refreshed after 50m
    but input was still not accepted and the display will not refresh. It resolved after 70m.
After this is seems to be OK, I can read mail etc.

To be sure, I made a copy of the profile where I deleted all the .msf files and observed the same thing.
I tried this a few times.

It is not just a one-off post-upgrade process. After it recovers and works, if I shut tb down and launch it
then it repeats the problem.

There are not too many emails here, maybe a few tens of thousand totaling just over 1GB (a few mailing lists).

My main mail client is on another machine, still running tb 91, and not showing this problem.

Searching the 'net I did not find a relevant report, where should I look?
Hi, I used TB Daily which is V106.0a1 and I don't notice this problem, but TB is a bit slow to shutdown. Just a silly question, have you tried V102 with a brand new empty profile, just to eliminate a corrupt configuration?

regards,
Steve


BTW, after reading the release notes, seeing the structural changes, I wonder if it is at all possible
to downgrade to v91?

TIA

(*) "not refreshed" means the panel is not painted after minimize/restore, showing only a border.

_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue



[Index of Archives]     [Older Fedora Users]     [Fedora Announce]     [Fedora Package Announce]     [EPEL Announce]     [EPEL Devel]     [Fedora Magazine]     [Fedora Summer Coding]     [Fedora Laptop]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Desktop]     [Fedora Fonts]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Yosemite News]     [Gnome Users]     [KDE Users]     [Fedora Art]     [Fedora Docs]     [Fedora Sparc]     [Libvirt Users]     [Fedora ARM]

  Powered by Linux