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 88
    • Issues 88
    • 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
  • #765

Closed
Open
Created Mar 27, 2017 by RingBot@RingBotOwner

Ring gets all available ram memory and then crash

Issue generated from Tuleap's migration script. Originally submitted by: Pablo Hinojosa Nava (pablohn)

A detailed description of the bug. Use following fields for description field:

Once installed ring I have not opened it yet (so it is not configured). The problem is when I reboot my computer, it gets all the memory and then the kernel must kill it.

* Environment:
Fedora 25 ring-20170322.1.ec25f0f-1.fc25.x86_64

* Reproduce steps:
Install ring.
Do not start nor configure it, just reboot.

* Expected result:
When reboot, ring process should have normal behaviour.

* Actual result:
gnome-ring --restore-last-window-state gets all ram memory till process must be killed. I attach a htop screenshot that shows gnome-ring getting more than 10GB of RAM.
Selection_986

Assignee
Assign to
Time tracking