[hafqa] [hafqa] [Bug 2915] runaway "enprocess" uses 100% CPU time

From: bugzilla-daemon at maemo.org bugzilla-daemon at maemo.org
Date: Wed Jun 25 14:47:17 EEST 2008
https://bugs.maemo.org/show_bug.cgi?id=2915


eero.tamminen at nokia.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |eero.tamminen at nokia.com




------- Comment #9 from eero.tamminen at nokia.com  2008-06-25 14:47 GMT+3 -------
(In reply to comment #4)
> > Ok, but the email client *is* open whenever this happens, right?
> 
> Nope, it's not. I guess the browser sends some request to the mail client.

Only reason for enprocess to run should be that you've enabled its regular
email checking/downloading feature (it could have been default when
configuring Email accounts), or you have Email application open.

Without more information, I would think this is the case, enprocess doesn't
have anything to do with the browser, it's just fetching your emails
"as requested"...?


> I have an imap account with about 3000 mails in the main inbox and several
> sub-boxes with about 15000 mails. So alltogether maybe slightly less than
> 20000 mails on this account.

Maybe it hadn't finished fetching and saving the emails when you
killed it and when it was restarted, it started the operation
from the beginning?


(In reply to comment #8)
> Now that Diablo is out and includes "Modest" instead of the old Email
> application that was shipped with Chinook I assume that no-one will work on
> this anymore and fix this - sorry.

And if this really was a real bug, I'd say that it's fixed by Modest,
not wontfix.  :-)

(+currently assigned to wrong person, Carlos has never been involved
with Email).


-- 
Configure bugmail: https://bugs.maemo.org/userprefs.cgi?tab=email
Replies to this email are NOT read, instead please add comments at
https://bugs.maemo.org/show_bug.cgi?id=2915
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.

More information about the hafqa mailing list