Memory leak in BOINC Manager

Bug #1574189 reported by shanen (Shannon Jacobs) on 2016-04-24
This bug affects 1 person
Affects Status Importance Assigned to Milestone
boinc (Ubuntu)

Bug Description

This behavior only began after installing 16.04 a few days ago. Watching BOINC Manager start with four running tasks, the memory utilization steadily creeps upward from about 30% and eventually it starts shutting down tasks, but has to be tricked into resetting the memory status.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: boinc-manager 7.6.31+dfsg-6
ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
Uname: Linux 4.4.0-21-generic x86_64
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
CurrentDesktop: Unity
Date: Sun Apr 24 17:11:29 2016
InstallationDate: Installed on 2015-05-05 (355 days ago)
InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1)
SourcePackage: boinc
UpgradeStatus: Upgraded to xenial on 2016-04-21 (2 days ago)

If it is related to the Menu bar bug I reported earlier, then this one should be folded into that one (Bug 1574160) and the Bug Heat of that one should be increased. My initial research suggested that was the primary problem, but I'm not certain that the apparent bug isn't a design change with an unclear rationale... Maybe the Menu bar break is somehow masked by Firefox?

marking as duplicate, lets see how the other bug will go.

At this time I'm inclined to regard this as a separate bug not directly related to the gdk menu bar problem. They appeared at the same time, but that was just because of the upgrade. Not sure how to prove that until I hear that Bug #1532226 has been closed and I see whether or not the problematic behavior persists.

Optimistically, this bug just reflects a fairly substantial reduction in free memory under 16.04.

Pessimistically, there's a memory leak that is most visible with long-running tasks such as BOINC units.

I've tweaked the BOINC memory settings on the optimistic assumption. Maybe that's enough?

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers