Description of problem: boinc-manager (the gui) increases memory usage in approximately 50k+ increments (at every kSysGuard refresh) until RAM is full. boinc-client runs without issue, only having a problem with boinc-manager (the gui) Version-Release number of selected component (if applicable): Boinc version: 7.2.33 x64 (installed via yum repository) Widgets ver 2.8.12 Fedora OS version: 3.12.8-300.fc20.x86_64 GNU/Linux How reproducible: After first noticing the problem, I was unable to gracefully exit boinc-manager. I issued a term sig on the process, shutdown and restarted. Steps to Reproduce: 1.After rebooting, started boinc via Konsole (run_client) 2.Then launched the boinc-manager gui from the desktop icon. 3. I launched KSysGuard to watch resource usage. boinc-manager started slowly filling up RAM in 50k+ increments. 4. Rinse / Repeat - I shut down boinc and rebooted again, restarted boinc following the above steps. The issue re-occured. On the repeated testing attempts, I was able to exit boinc-manager normally, as the memory wasn't completely full at the point of shutdown. Actual results: boinc-client usable, boinc-manager fills ram Expected results: Normal memory usage Additional info: Note that the boinc-client runs without issue, and has been returning valid results. If I only run the client, boinc-app memory usage is normal (approximately 250mb collectively for 3 simultaneous-running apps.) System summary: HP Desktop with AMD processor installed RAM: 9 GB The hard drive free space is over 75% Aside from memory / HD upgrade, the computer is as-factory-issued (i.e. no overclocking or oddities) The OS (Fedora SDK) was just freshly installed 3 days ago, and apart from this issue, is other-wise stable. Also, here is the pasted information I extracted on the boinc-manager process via kSysGuard: Process - boincmgr Summary The process boincmgr is using approximately 7.7 GB of memory. It is using 7.7 GB privately, 56.8 KB for pixmaps, and a further 1500.0 KB that is, or could be, shared with other programs. (= 468 KB clean + 8037924 KB dirty) Dividing up the shared memory between all the processes sharing that memory we get a reduced shared memory usage of 283.0 KB. Adding that to the private and pixmap usage, we get the above mentioned total memory footprint of 7.7 GB. 530.0 MB is swapped out to disk, probably due to a low amount of available memory left. Library Usage The memory usage of a process is found by adding up the memory usage of each of its libraries, plus the process's own heap, stack and any other mappings. Private more 8037452 KB [heap] 268 KB /SYSV00000000 (deleted) 116 KB /usr/lib64/libwx_gtk2u_core-2.8.so.0.8.0.#prelink#.foiX5s (deleted) 60 KB /usr/bin/boincmgr (deleted) 32 KB /usr/lib64/libgtk-x11-2.0.so.0.2400.22.#prelink#.ZTuJMg (deleted) Shared more 512 KB /SYSV00000000 (deleted) 408 KB /usr/lib64/libc-2.18.so 152 KB /usr/lib64/libglib-2.0.so.0.3800.2 76 KB /usr/lib64/libX11.so.6.3.0 64 KB /usr/lib64/libm-2.18.so Totals Pixmap 57 KB (Might be stored in the graphics card's memory) Private 8038392 KB (= 468 KB clean + 8037924 KB dirty) Shared 1500 KB (= 988 KB clean + 512 KB dirty) Rss 8039892 KB (= Private + Shared) Pss 8038675 KB (= Private + Shared/Number of Processes) Swap 542700 KB
My apologies, but I forgot to mention that initially I attempted to install Boinc from the installer on the Boinc website. Though that install appeared to be successful, I was unable to get it to run. The "BOINC" directory created by the installer in /var/lib was empty and I was unable to find the rpc_auth file with the password to connect the manager app to the client. I then installed boinc from the repository via yum.
Closing ticket -I was able to fix the issue myself. As noted in above comment, I initially tried to install the version from the Boinc website. When that failed, I installed Boinc from the repository. Based on checking datestamps for all boinc* files on the hard drive, I discovered that there were remnants from the other install present in /var/lib that were causing the issue. Long story short, the were files from boinc version 7.2.33 x64 (the failed install from boinc website package) and files from version 6.10.58 (repository install) that I was running. The client version running the tasks was actually 6.10.56, and when I launched the manager from the desktop it was 7.2.33. The confusing part for me was that everything worked without any visible errors. Although the newer manager connected and functioned with the old client, it was dumping endless data into RAM. My apologies for the newb mistake, and if I wasted anybody's time. I'm fairly new to the Linux environment and still learning. (20+ years of working in a Windows environment)