Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • meld meld
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 199
    • Issues 199
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 4
    • Merge requests 4
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • GNOMEGNOME
  • meldmeld
  • Issues
  • #565
Closed
Open
Issue created Mar 09, 2021 by Tomas Vondra@tvondra

meld 3.21.x still running after getting closed, using 100% CPU

I've noticed that if I close meld right after it gets opened (e.g. from git difftool, it sometimes keeps running and consuming 100% CPU). It seems like some sort of race condition, because you have to close it right after it opens and renders the contents - if you wait a couple seconds, it closes just fine.

I've only ever reproduced on meld 3.21.x (Fedora 33). The previous version (3.20.3) seems to be working fine. I'm using meld mostly from git difftool, not sure if that's relevant.

Attached is a perf profile from the running meld process - it seems to be doing a lot of locking/unlocking, and polling for data on a file descriptor or somethingprofile.txtprofile.txt.

Assignee
Assign to
Time tracking