Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in / Register
J
jami-client-gnome
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 152
    • Issues 152
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
    • Iterations
  • Requirements
    • Requirements
    • List
  • Security & Compliance
    • Security & Compliance
    • Dependency List
    • License Compliance
  • Operations
    • Operations
    • Incidents
  • Analytics
    • Analytics
    • Insights
    • Issue
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
  • savoirfairelinux
  • jami-client-gnome
  • Issues
  • #1183

Closed
Open
Opened Apr 30, 2020 by jami user@duroc

crashes apparently due to memory bloat (perhaps a memory leak)

I'm running Jami on 11 year old hardware with 4GB RAM. My Debian system periodically grinds to a halt with the HDD LED pegged, as if it's swapping a seemingly impossible amount of data. When this happens the system logs are flooded with lines that look like this:

jami-gnome.desktop[2780]: Memory pressure relief: Total: res = 22794240/22794240/0, res+swap = 18784256/18788352/4096"

I never really use Jami because I don't know anyone who uses it. So it's always just idling. This bug may be a memory leak and it may be difficult to reproduce and troubleshoot. Perhaps the best approach would be to add a parameter for users to specify the amount of RAM the app is allowed to consume. If it's written in java i think the wiring is already in place for that. I also suggest logging feature that tracks the memory footprint. The man page shows there is a --debug option, but it does not state what information is logged or where it's logged.

Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: savoirfairelinux/ring-client-gnome#1183