Bug 1090203
Summary: | Evo hangs one whole workspace when a particular e-mail is selected in preview (ews?) | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Bojan Smojver <bojan> |
Component: | evolution | Assignee: | Matthew Barnes <mbarnes> |
Status: | CLOSED DUPLICATE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | high | Docs Contact: | |
Priority: | unspecified | ||
Version: | 20 | CC: | fabiano, lucilanga, mbarnes, mcrha |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i686 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2014-04-23 16:30:43 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Bojan Smojver
2014-04-22 22:40:21 UTC
One more thing. The "frozen workspace" behaviour is not the only way this bug manifests itself. Sometimes, it is just Evo that hangs. It displays "retrieving message <id>" down in the status bar and hangs. Clicking anywhere else in Evo does nothing. This must be some kind of message display problem. I just turned preview off, positioned myself on the message and displayed source of it just fine (Ctrl + U). However, a double click on it (view), immediately hangs the interface. Thanks for a bug report. I suppose the message's preview also causes high CPU usage. It would be good to install debuginfo packages for evolution-data-server and evolution, and get a backtrace of "running" evolution, like with: $ gdb --batch --ex "t a a bt" -pid=`pidof evolution` &>bt.txt It (the bt.txt file) can contain some private information, thus make sure you'll not expose any (I usually search for "pass" at least (quotes for clarity only)). I suspect that webkit got stock in accessibility/a11y code, I recall some upstream bugs related to it. (In reply to Milan Crha from comment #3) > I suppose the message's preview also causes high > CPU usage. When any of the hangs happen, CPU usage is practically non-existent. Backtraces sent privately. Thanks, the backtraces helped to identify the issue. It is the same as bug #1089966, see the bug #1089966 comment #2 for a workaround. *** This bug has been marked as a duplicate of bug 1089966 *** |