Uploaded image for project: 'Hippo CMS'
  1. Hippo CMS
  2. CMS-9539

Extreme cpu usage in Hippo 10 using Chrome

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Blocker
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 3.1.0
    • Component/s: None
    • Environment:
      Windows 7 Enterprise
      Chrome 45
      core i7
    • Similar issues:
    • Sprint:
      Tiger Sprint 113

      Description

      Chrome and browsers based on the same technology seem to have an extreme cpu usage when using the cms. This happens when you open a document for viewing or editing.

      The cpu usage seems to be around 12-13 percent on desktops and about 25% on laptops. Most users have laptops and desktops are meant to be phased out. Users may be logged in to multiple cms instances, but the cpu usage does depend on focus so this doesn't seem to stack.

      The cpu usage is constant, not incidental.

      Chrome is the standard browser for users.

      The issue does not occur in FF 40 or Internet Explorer 11

      Reproduction steps Ubuntu 14.04/Chrome 45.0.2454.99 (64-bit)
      1. Login in on the CMS with Go Green (https://cms.demo.test.onehippo.com/)
      2) Open a document for viewing for example: /content/documents/hippogogreen/events/2014/11/bio-and-eco-expo-2014
      Observed: CPU usage constant high level (25%)
      3) Switch o an empty Chrome tab
      Observed: CPU drops
      4) View the same document with Firefox 41.0
      Observed: Still constant CPU usage but at a less than in Chrome

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                pgupta Pankaj Gupta (Inactive)
                Reporter:
                hippo-helpdesk@bloomreach.com Hippo Helpdesk
              • Votes:
                0 Vote for this issue
                Watchers:
                7 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: