Posts by Burstaholic

1) Message boards : Number crunching : Possible Memory Leak with Nvidia GPU (Message 64807) Posted 5 Jul 2016 by Burstaholic Post: Haven't tried the older client, but A/B testing confirms the problem is with the separation application. I left N-body running for the full long weekend and it's still at 41.1M RAM usage. Running just 'Separation (Modified Fit)' eats RAM fast. (I didn't realize about the 'Reset project' button, so switching tasks to confirm things took a while.)
2) Message boards : Number crunching : Possible Memory Leak with Nvidia GPU (Message 64717) Posted 21 Jun 2016 by Burstaholic Post: Additional information: should have mentioned I determined those numbers during the day, not actually by leaving it overnight. It looks like suspending and resuming GPU jobs may be the culprit - when I suspend a job, memory usage drops 25MB, but when I resume, it goes up by 50 MB. So having dynamic 'Suspend when computer is busy' will cause some serious memory growth if it cycles very often. I can try using the older client, though I'm not sure why the download on the site is four minor versions behind. 7.6.31 is the version in the Ubuntu 16.04 repos, and was released Mar 3 (https://github.com/BOINC/boinc/releases/tag/client_release%2F7.6%2F7.6.31). 7.6.33 was released June 5, in fact. So that line is definitely not old, though it may not be considered stable in some way? I don't understand their versioning scheme.
3) Message boards : Number crunching : Possible Memory Leak with Nvidia GPU (Message 64710) Posted 21 Jun 2016 by Burstaholic Post: Well, that was easy. It's definitely the GPU jobs. With GPU suspended the service's RAM usage stays below 40 MB, but with GPU enabled it climbs to ~600 MB within a couple of hours. My GPU is an Nvidia Quadro 2000; I can give you more system details if they would be helpful. Killing boinc-client and simply restarting X (via logout/login) seems to clear it up, which is what led me to suspect the GPU app initially. Maybe a bug in the code that interacts with Xorg?
4) Message boards : Number crunching : Possible Memory Leak with Nvidia GPU (Message 64697) Posted 20 Jun 2016 by Burstaholic Post: Not sure how to tell. I can easily disable GPU jobs overnight and see what happens; is there a way to pick only one of the CPU applications to isolate those?
5) Message boards : Number crunching : Possible Memory Leak with Nvidia GPU (Message 64688) Posted 20 Jun 2016 by Burstaholic Post: Looks like I'm also seeing this issue - my desktop is using quite a bit of swap space, and I don't think MilkyWay@Home is meant to be using 7.7 GB of RAM? I'm running only this project, with default settings (Ubuntu 16.04): -> sudo service boinc-client status â— boinc-client.service - Berkeley Open Infrastructure Network Computing Client Loaded: loaded (/lib/systemd/system/boinc-client.service; enabled; vendor preset: enabled) Active: active (running) since Thu 2016-06-16 09:11:06 CDT; 4 days ago Process: 14284 ExecStopPost=/bin/rm -f /var/lib/boinc-client/lockfile (code=exited, status=0/SUCCESS) Process: 10403 ExecStartPre=/bin/chown boinc:boinc /var/log/boinc.log /var/log/boincerr.log (code=exited, status=0/SUCCESS) Process: 10400 ExecStartPre=/usr/bin/touch /var/log/boinc.log /var/log/boincerr.log (code=exited, status=0/SUCCESS) Main PID: 10409 (sh) Tasks: 3 Memory: 7.7G CPU: 2w 3h 33min 57.426s CGroup: /system.slice/boinc-client.service â”œâ”€10409 /bin/sh -c /usr/bin/boinc --dir /var/lib/boinc-client >/var/log/boinc.log 2>/var/log/boincerr.log â””â”€10414 /usr/bin/boinc --dir /var/lib/boinc-client