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 343428 - high CPU utilization
high CPU utilization
Status: RESOLVED INVALID
Product: evolution
Classification: Applications
Component: general
2.6.x (obsolete)
Other other
: Normal major
: ---
Assigned To: Harish Krishnaswamy
Evolution QA team
Depends on:
Blocks: 343991
 
 
Reported: 2006-05-30 19:05 UTC by ralph.sokel
Modified: 2006-06-14 14:21 UTC
See Also:
GNOME target: ---
GNOME version: 2.11/2.12


Description ralph.sokel 2006-05-30 19:05:59 UTC 
Distribution: Unknown
Package: Evolution
Severity: major
Version: GNOME2.12.0 2.6.x
Gnome-Distributor: SUSE
Synopsis: high CPU utilization
Bugzilla-Product: Evolution
Bugzilla-Component: Miscellaneous
Bugzilla-Version: 2.6.x
Description:
Description of Problem:
Using evolution 2.6.0-18, data server 1.6.0-24 and exchange connector
2.6.0-30. After updating the connector I have noticed that evolution
consistently uses close to 100% of my cpu.

Steps to reproduce the problem:
Just running evolution

Actual Results:


Expected Results:


How often does this happen? Always. Rebooting the system has not
helped.


Additional Information:




------- Bug created by bug-buddy at 2006-05-30 19:05 -------
Comment 1 André Klapper 2006-05-30 20:26:08 UTC 
very vague :-/
Comment 2 ralph.sokel 2006-05-30 21:18:30 UTC 
vague but very annoying. there may be some issue with communications with our exchange server because the high and continuous cpu usage only occurs when i enable my exchange account. there is no problem with using imap access with evolution to my email. i was hoping someone would have some suggestions on how to debug the problem because i don't have access to any IT support for linux where i work.
Comment 3 Michele Baldessari 2006-06-07 20:03:06 UTC 
Hi Ralph,

one way to have at least a basic idea of what is going on is to run the 'top' command. Once you identify the process (if it is a single one), take note of
the PID (first column on the left), quit top and run the following:

strace -p <PIDNR> -v -f -o strace.log 


(hopefully your distro has strace installed ;))

Keep this command running for a while and then attache the newly-created
"strace.log" file to this bug, so we hopefully might get a better idea of what's
going on. 

thanks
Comment 4 ralph.sokel 2006-06-07 20:24:39 UTC 
Michele,

Thanks for the pointer to strace. When this problem happened I was trying to update evolution from 2.4 to 2.6 in suse 10.0. In addition to the 'cpu runaway' I also experienced other issues so I finally just updated to 10.1 which has evolution 2.6. Evolution behaved perfectly. Unfortunately commercial CAD applications that I use would not work with glibc 2.4 (threads library stuff I suspect since I have to use the LD_ASSUME_KERNEL to get them to work with suse 10.0). So I am back to 10.0 and will stick with evolution 2.4 for a while.

It is very confusing and disappointing that the entire gnome update path within suse 10.0 seems to be really broken. Almost all attempts to update a package results in numerous dependency issues.

Bottom line is that I think this bug report can be closed since I don't suspect that there is anything intrinsically related to evolution that resulted in the cpu utilization issue that I saw.
Comment 5 Michele Baldessari 2006-06-14 14:21:22 UTC 
Ralph,

thanks for taking the time to respond. I'll go ahead and close it now.
Feel free to reopen it if you stumble upon the issue again.