Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in / Register
  • J jami-client-gnome
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 89
    • Issues 89
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Deployments
    • Deployments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Insights
    • Issue
    • Repository
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • savoirfairelinux
  • jami-client-gnome
  • Issues
  • #454

Closed
Open
Created Jun 02, 2016 by RingBot@RingBotOwner

Calling a Ring account take significant amount of CPU

Issue generated from Tuleap's migration script. Originally submitted by: Emmanuel Lepage Vallee (elv13)

I tried to call myself using a Ring account and the fan went crazy. I think it is a regression. The call failed then the CPU went down again. But for 30 seconds, I Ring was taking a full core.

See the sysprof screenshot for details.

cpu

Assignee
Assign to
Time tracking