| Summary | IMP auth uses too much CPU and MEM resources |
| Queue | IMP |
| Queue Version | 4.1 |
| Type | Bug |
| State | Not A Bug |
| Priority | 1. Low |
| Owners | |
| Requester | zoli (at) polarhome (dot) com |
| Created | 03/15/2006 (7085 days ago) |
| Due | |
| Updated | 03/15/2006 (7085 days ago) |
| Assigned | 03/15/2006 (7085 days ago) |
| Resolved | 03/15/2006 (7085 days ago) |
| Github Issue Link | |
| Github Pull Request | |
| Milestone | |
| Patch | No |
State ⇒ Not A Bug
What does it mean? Have you seen this behaviour earlier?
What am I doing wrong?
State ⇒ Feedback
Priority ⇒ 1. Low
State ⇒ Unconfirmed
Priority ⇒ 3. High
Type ⇒ Bug
Summary ⇒ IMP auth uses too much CPU and MEM resources
Queue ⇒ IMP
recently I decided to upgrade my horde installation that worked perfect.
Now I run the following configuration:
Forwards: H3 (3.0-RC1)
Gollem: H3 (1.0.2) (run Gollem tests)
Horde: 3.1
Imp: H3 (4.0.4) (run Imp tests)
Ingo: H3 (1.1) (run Ingo tests)
Kronolith: H3 (2.1)
Mimp: H3 (1.0-RC1) (run Mimp tests)
Mnemo: H3 (2.1)
Nag: H3 (2.1)
Turba: H3 (2.1) (run Turba tests)
PHP Version: 4.3.10 (CGI interface)
I use IMP to log in into the Horde. IMP uses IMAP against a remote host.
I find that when I upgrade to IMP to H3 (4.1) I can log in to a server
if I do not have mail in the inbox, but if I have mail in the inbox
PHP process tops to 100% cpu usage and RSS memory is raising without
limit... and it can not log in.
If I switch back to IMP H4 (4.0.4) everything works perfect.
Actually IMP 4.1 appears to be unusable.
I use horde for ages and I am aware that you test well released
products - but I am also aware that CGI interface might be forgotten
from time to time. I guess that this happened again.
Any help or workaround would be appreciated...
Best regards,
Zoltan Arpadffy