need information on setting up log files
Page 1 of 1 (4 posts)
Tags:
None
Registered Member 
|
Hi all:
Currently my system has a serious memory leak in the Plasmashell task and has consumed about 58% of my 31.3 gigs of system RAM. The particulars are
I need to set up some type of logging to see exactly where the leak is occurring. Does anyone have a manual or kept some notes on how to begin this process? Thank you |
|
Registered Member
|
I followed the procedures listed in https://community.kde.org/Plasma/Debugging for troubleshooting, and the log file keeps increasing.
Does anyone have an idea on what is going wrong here? I am NOT sure which errors or log lines which need attention. All I know is that more system RAM is being slowly chewed away. |
|
Registered Member
|
I am learning about the information given in the /proc/self/maps or /proc/pid/maps section, when looking at the process. In my case the leaky memory is occurring in the viritual memory area.
As I have been learning, I came across this wonderful tool, see https://github.com/DataDrake/proc-maps. Another informative site was https://www.fatalerrors.org/a/brief-analysis-of-memory-management-proc-pid-maps.html which is a good explanation of what is going on and what information the /proc/self/maps or /proc/pid/maps provides. The pertinant information states:
I enclose a simple script file which creates a log every so many seconds apart, it is a bash script
You are welcome to use this bash script as you wish and modify to your desire. I am getting closer to understanding where the leak is occurring, it occurs in a certain section of the maps file
The problem line is this one:
where the size in red font keeps slowly increasing over time. Unfortunately the SYSV00000000 segment seems to be virtual memory, but I need to understand more what is happening here. The bash script file above enabled me to locate the part which was slowly eating up memory, next I will focus on what is causing this problem, although the /proc/pid/map seems to point to a plugin as the problem, see the information just above the /SYSV00000000 line. |
|
Registered Member
|
After having set up proc-maps program and watching, and the hint that the error was in viritual memory, I turned OFF the slide-show option for the KDE Desktop.
The following log file shows that the leaker has been correctly identified. (after turning off slide show and leaving desktop background fixed to only 1 image file)
I now consider that the memory leaker has been located. It is time for me to talk to the KDE developers about the software rendering in the slideshow portion or option of the KDE desktop setup. My question as to identifying the memory leaker has been answered.  I consider this thread closed.
|
Page 1 of 1 (4 posts)
Bookmarks
Who is online
Registered users: Bing [Bot], Evergrowing, Google [Bot], rblackwell
