Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in / Register
  • J jami-client-qt
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 165
    • Issues 165
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Infrastructure Registry
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • savoirfairelinux
  • jami-client-qt
  • Issues
  • #649

Closed
Open
Created Jan 17, 2022 by Maxim Cournoyer@mcournoyerMaintainer

Excessive memory usage (leak?) when there are many photos/videos in conversations

  • OS: Guix at commit 8cdecad237343f5c955d17df3a78e41fa1f2d56c.
  • Jami version:20211223.2.37be4c3
  • What build you are using: Guix

Steps to reproduce

  • Can you reproduce the bug: at will
  • Steps:
    1. Open a conversation with tens of high resolution photos or videos. 2. Notice RAM memory usage going from 304 MiB (at start) to close to 3 GiB as you scroll through
  • Actual result: RAM usage is too high / app becomes sluggish, sometimes gets killed by OOMK
  • Expected result: RAM usage should remain reasonable (perhaps load only thumbnails of photos instead of the full thing in memory, if that's what it's currently doing?)
Edited Jan 17, 2022 by Maxim Cournoyer
Assignee
Assign to
Time tracking