Created attachment 857354 [details] screenshot Description of problem: Evolution hangs and became consume a lot of CPU resources.
Thanks for a bug report. COuld you grab a backtrace of evolution in such state, please? It'll show what it does. I expect the Thread 1 being busy with something what prevents UI to update.
Created attachment 857430 [details] backtrace of evolution
Created attachment 857431 [details] screenshot
*** Bug 1059706 has been marked as a duplicate of this bug. ***
Thanks for the update. I see from the backtrace that webkit is doing a clean-up after you moved from one message to another. From that I believe this is related to that certain message, which is causing trouble for some reason. I suppose you can guess from the screen shot which message you had selected before this hang happened, thus could you try to reproduce this, basically find the problematic message, please? There is one thing, I noticed couple reports about memory corruption, thus maybe this is related too, that you reproduced in some way this memory corruption which exhibits in this hang (but I'm only wild-guessing now). It would be good to also watch evolution's console, when you run it from a terminal, to see whether it'll not print there anything interesting.
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
This bug appears to have been reported against 'rawhide' during the Fedora 22 development cycle. Changing version to '22'. More information and reason for this action is here: https://fedoraproject.org/wiki/Fedora_Program_Management/HouseKeeping/Fedora22
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.