6.0.0-beta1
7/4/25

[#14317] 100% CPU usage
Summary 100% CPU usage
Queue Turba
Queue Version 4.2.14
Type Bug
State Duplicate
Priority 2. Medium
Owners
Requester azurit (at) pobox (dot) sk
Created 04/06/2016 (3376 days ago)
Due
Updated 04/06/2016 (3376 days ago)
Assigned 04/06/2016 (3376 days ago)
Resolved 04/06/2016 (3376 days ago)
Github Issue Link
Github Pull Request
Milestone
Patch No

History
04/06/2016 01:17:20 PM Michael Rubinsky Comment #7
State ⇒ Duplicate
Reply to this comment
04/06/2016 12:56:29 PM azurit (at) pobox (dot) sk Comment #6 Reply to this comment
pls close this, i will open a new bug for The Horde Framework 
libraries and packages
04/06/2016 12:36:51 PM azurit (at) pobox (dot) sk Comment #5 Reply to this comment
2016-04-06T14:34:29+02:00 EMERG: HORDE [imp] Maximum execution time of 
120 seconds exceeded [pid 7743 on line 96 of 
"/usr/share/php/Horde/Css/Parser/vendor/sabberworm/php-css-parser/lib/Sabberworm/CSS/Parser.php"]
04/06/2016 12:29:07 PM azurit (at) pobox (dot) sk Comment #4 Reply to this comment
Also this:

2016-04-06T14:23:08+02:00 EMERG: HORDE [imp] Maximum execution time of 
120 seconds exceeded [pid 20617 on line 18 of 
"/usr/share/php/Horde/Css/Parser/vendor/sabberworm/php-css-parser/lib/Sabberworm/CSS/Parsing/UnexpectedTokenException.php"]

2016-04-06T14:23:08+02:00 DEBUG: HORDE 1. 
Horde_ErrorHandler::catchFatalError()
04/06/2016 12:27:27 PM azurit (at) pobox (dot) sk Comment #3 Reply to this comment
Ok, i have this:
2016-04-06T14:23:09+02:00 EMERG: HORDE [imp] Maximum execution time of 
120 seconds exceeded [pid 20629 on line 578 of 
"/usr/share/php/Horde/Css/Parser/vendor/sabberworm/php-css-parser/lib/Sabberworm/CSS/Parser.php"]

Probably not the Turba's fault cos i tried to downgrade it back to 
4.2.13 and problem persists. I also tried to downgrade IMP to 6.2.13 
with no luck.
04/06/2016 11:56:57 AM Jan Schneider Comment #2
Priority ⇒ 2. Medium
State ⇒ Feedback
Reply to this comment
Cannot reproduce. Limit the execution time and see where it loops.
04/06/2016 11:20:24 AM azurit (at) pobox (dot) sk Comment #1
Priority ⇒ 3. High
Type ⇒ Bug
Summary ⇒ 100% CPU usage
Queue ⇒ Turba
Milestone ⇒
Patch ⇒ No
State ⇒ Unconfirmed
Reply to this comment
After upgrade to 4.2.14 (from previous version), lots of processes 
(but not all) started to use 100% CPU. I'm not sure if this is Turba's 
false but this is the last logged line from such processes:

2016-04-06T13:11:02+02:00 DEBUG: HORDE [turba] SQL  (0,0099s)
         SELECT object_id, object_type, owner_id, object_members,
           object_nameprefix, object_firstname, object_middlenames,
           object_lastname, object_namesuffix, object_company, 
object_email FROM
           turba_objects WHERE (((LOWER(object_nameprefix) LIKE
           LOWER('%<censored-email-address>%') OR LOWER(object_firstname) LIKE
           LOWER('%<censored-email-address>%') OR 
LOWER(object_middlenames) LIKE
           LOWER('%<censored-email-address>%') OR LOWER(object_lastname) LIKE
           LOWER('%<censored-email-address>%') OR LOWER(object_namesuffix) LIKE
           LOWER('%<censored-email-address>%')) OR object_email = 
'<censored-email-address>')
           AND owner_id = '<censored-login>') [pid 19395 on line 321 
of "/usr/share/php/Horde/Db/Adapter/Mysqli.php"]

When trying to strace the process, nothing is displayed. Processes are 
running (and taking 100% CPU) until killed.

Saved Queries