User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/103.0.0.0 Safari/537.36 Steps to reproduce: Switch from Thunderbird 112.13.0 to 115.0.1 Actual results: While Thunderbird 112.13.0 ran without issues Thunderbird 115.0.1 takes 100% of one core and is unresponsive for tenth of minutes. As soon als core occupancy drops beyond 8% Thunderbird is responsive again. But this does not keep. Load increases after about a minute or two and Thunderbird is again unresponsive for tenth of minutes. Expected results: Thunderbird staying responsive, even if occupying one core 100% for actions if more than one core is available. If only one core is available Thunderbird should be able to stay responsive by giving user actions higher priority.
Bug 1844842 Comment 0 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/103.0.0.0 Safari/537.36 Steps to reproduce: Switch from Thunderbird ~~~112.13.0~~~ 102.13.0 to 115.0.1 Actual results: While Thunderbird ~~~112.13.0~~~ 102.13.0 ran without issues Thunderbird 115.0.1 takes 100% of one core and is unresponsive for tenth of minutes. As soon als core occupancy drops beyond 8% Thunderbird is responsive again. But this does not keep. Load increases after about a minute or two and Thunderbird is again unresponsive for tenth of minutes. Expected results: Thunderbird staying responsive, even if occupying one core 100% for actions if more than one core is available. If only one core is available Thunderbird should be able to stay responsive by giving user actions higher priority.