After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 793450 - High CPU load 3.26.5-1 evolution-source-registry
High CPU load 3.26.5-1 evolution-source-registry
Status: RESOLVED DUPLICATE of bug 793466
Product: evolution-data-server
Classification: Platform
Component: general
3.26.x (obsolete)
Other Linux
: Normal major
: ---
Assigned To: Evolution Shell Maintainers Team
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2018-02-14 14:13 UTC by Alejandro
Modified: 2018-02-19 14:11 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Alejandro 2018-02-14 14:13:25 UTC
Since version 3.26.5-1 evolution-source-registry is causing two CPU threads to run at 100%. I am using the goa with a google account, microsoft account and 2 normal imap e-mail addresses. In version 3.26.4-1 everything works fine.
Comment 1 Alejandro 2018-02-14 14:36:57 UTC
Deleting and reconfiguring the microsoft exchange account solved the issue
Comment 2 Milan Crha 2018-02-15 16:27:27 UTC
Thanks for a bug report.

(In reply to Alejandro from comment #1)
> Deleting and reconfiguring the microsoft exchange account solved the issue

I'm afraid you cannot reproduce it any more, can you? What Exchange account type it was, please? There can be used evolution-ews or evolution-mapi.

In case you manage to reproduce this, get the backtrace, please. It will show what it tries to do. Alternatively, do you have stored the backtrace anywhere? You might install debuginfo packages for evolution-data-server and the exchange connector packages, the the backtrace is usable. I guess from comment #0 that you know how to get the backtrace of a running process, but in case I'm wrong just let me know, I can provide gdb command for it. Thanks in advance.
Comment 3 Milan Crha 2018-02-16 14:09:51 UTC
I think this is the same as bug #793466. I used that bug, because the reporter there found the cause. Let me know if it's a different kind of issue for you. Thanks in advance.

*** This bug has been marked as a duplicate of bug 793466 ***
Comment 4 Alejandro 2018-02-19 09:24:32 UTC
I am sorry I can't reproduce this bug. I was using evolution-ews. If it reappears I will attach a backtrace.
Comment 5 Milan Crha 2018-02-19 14:11:53 UTC
Thanks for the update. It seems the circumstances are very similar (there had been used evolution-ews too), thus your issue might be pretty the same issue as the other bug.