Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • xfce4-session xfce4-session
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 81
    • Issues 81
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 3
    • Merge requests 3
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Releases
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Xfce
  • xfce4-sessionxfce4-session
  • Issues
  • #133
Closed
Open
Created Apr 02, 2022 by Maximilian Knespel@mxmlnkn

Memory usage keeps growing

I'm currently logged in for 108 days and over that time I observed a very slow creep of xfce4-session memory usage over each day. At the current time, it takes up 4GB of memory! So akin to 40 MB per day.

It looks like a memory leak to me, which forces me to reboot the system sometime in the future. Unfortunately, I don't have any more information on this and I'm not running a debug version, so I doubt I could glean anything useful from it with a memory dump.

I'm completely guessing at this point but it could be something trivial like some internal memory-held log growing over time. I had a similar problem with the .xsession-errors files in the past because pidgin keeps spamming Json-CRITICAL "warnings". Currently, .xsession-errors is 45MB large, which is still ok. Xfce4-session is "only" mentioned about 4000 times with (the Pidgin log line appears 380k times):

(xfce4-session:14089): xfce4-session-WARNING **: 01:10:58.993: ICE connection 0x56327fb692f0 rejected

and 5 times

(xfce4-session:14089): GLib-WARNING **: 19:10:20.560: GChildWatchSource: Exit status of a child process was requested but ECHILD was received by waitpid(). See the documentation of g_child_watch_source_new() for possible causes.
Assignee
Assign to
Time tracking