This bug was fixed in the package software-center - 5.2.7
---
software-center (5.2.7) precise-proposed; urgency=low
* lp:~mvo/software-center/oem-descriptor-in-user-agent-5.2:
- include the oem-channel descriptor in the custom user agent
string (LP: #1042749)
* lp:~mvo/s
Sorry for the delay:
Yeap I'm getting similar readings:
In [6]: myutils.statinfo('software-center')
Application software-center is not running
In [7]: myutils.statinfo('software-center')
Application Name: software-center
Cpu Percentage: 46.2948
Memory size: 169.0
In [8]: myutils.statinfo('so
Memory usage seems to increase a lot less with the -proposed version
(htop RES):
162M (initial)
205M (after first install)
209M (2nd)
215M (3rd)
216M (4th)
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ub
Hello Dave, or anyone else affected,
Accepted software-center into precise-proposed. The package will build
now and be available at http://launchpad.net/ubuntu/+source/software-
center/5.2.7 in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
htt
I've rejected the software-center SRU from the precise-proposed queue,
as bug #1006570 and bug #1042279 have been waiting for test cases and
regression potential for over a month now.
Once these bugs have the necessary information for an SRU, please ping
me or another an SRU team member in #ubuntu
** Also affects: software-center (Ubuntu Precise)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1003466
Title:
Software Center Memory/Processor bug
To ma
This bug was fixed in the package software-center - 5.3.12
---
software-center (5.3.12) quantal; urgency=low
[ Michael Vogt ]
* lp:~mvo/software-center/inspect-memleak:
- fix two memory leaks when the cache is re-opened after
a package has been installed/removed (LP: #10
** Branch linked: lp:software-center/5.2
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1003466
Title:
Software Center Memory/Processor bug
To manage notifications about this bug go to:
https://bugs
Confirmed the current fix greatly reduces the leak it is however still
there partially :) It knocks about 200 meg off the size.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1003466
Title:
Software
** Branch linked: lp:software-center
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1003466
Title:
Software Center Memory/Processor bug
To manage notifications about this bug go to:
https://bugs.lau
** Changed in: software-center (Ubuntu)
Status: Triaged => In Progress
** Branch unlinked: lp:~mvo/software-center/memleak-fixes-lp1003466
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1003466
Just found a second source of a leak, I think the big ones are now under
control, at least in the testcases I created so far.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1003466
Title:
Software Ce
** Branch linked: lp:~mvo/software-center/inspect-memleak
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1003466
Title:
Software Center Memory/Processor bug
To manage notifications about this bug go
Similar to the observation in #11
(https://bugs.launchpad.net/ubuntu/+source/software-center/+bug/1003466/comments/11)
it seems that
a) its important that there are some "recomendations for you" in the details
page (e.g. for "2vcard" the code shows very little growth)
b) that _add_tiles_to_f
I found one source:
$ PYTHONPATH=. python tests/gtk3/test_memleak.py RealMemleakTestCase
inspecting AppdetailsView.show_app()
nr_objs: 67491 size: 148.3M res: 1.4G (37963 378064)
2012-09-06 15:23:38,187 - softwarecenter.db.pkginfo_impl.aptcache - INFO -
aptcache.open()
2012-09-06 15:23:40,934 - s
A (maybe) useful script:
http://code.activestate.com/recipes/546530/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1003466
Title:
Software Center Memory/Processor bug
To manage notifications about
I have some code to trace that now in lp:~mvo/software-center/inspect-
memleak:
Usually when I run it it looks roughly like this:
$ PYTHONPATH=. python tests/gtk3/test_memleak.py 2>/dev/null
inspecting SoftwareCenterAppGtk3._on_transaction_finished()
nr_objs: 58141 size: 125.5M res: 360.7M (32125
The more I look into this the more I get the impression the normal python tools
are not helping,
neither objgraph nor meliae give good hints.
Meliae is really awsome, and yet:
>>> om_startup.summarize()
Total 423202 objects, 394 types, Total size = 41.9MiB (43896060 bytes)
>>> om_after_three_ins
No, not there yet I think
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1003466
Title:
Software Center Memory/Processor bug
To manage notifications about this bug go to:
https://bugs.launchpad.net/
I attached lp:~mvo/software-center/memleak-fixes-lp1003466 that is worth
testing, that kills off most of the growth for me in my (artificial)
testing. Dave, when you do install testing next, would be nice to give
this branch a try :)
** Branch linked: lp:~mvo/software-center/memleak-fixes-lp100346
With those lines commented out the memleak is more or less gone. Obviously that
is not a fix,
but its hopefulyl enough to disconnect the signals in destory() and figure out
what the issue
with the details is.
** Patch added: "a "fix" that isolates the problematic spots"
https://bugs.launchpa
And looking even further its the FeaturedTile() creation that is the problem,
for some reason in combination
with the db/cache refresh. It looks like somehow it keeps old references
preventing the cache to get
properly deleted. Its unclear yet how this happens as the code looks relatively
innoc
Going deeper into this rabithole it appears its actually:
def _on_app_recommendations_agent_refresh(self, cat):
docs = cat.get_documents(self.catview.db)
# display the recommendations
if len(docs) > 0:
self.catview._add_tiles_to_flowgrid(docs,
Looking further it appears that the get_addons() call in aptcache.py is mostly
responsible.
Removing it:
=== modified file 'softwarecenter/db/pkginfo_impl/aptcache.py'
--- softwarecenter/db/pkginfo_impl/aptcache.py 2012-04-18 08:44:00 +
+++ softwarecenter/db/pkginfo_impl/aptcache.py 2012-05-
** Tags added: patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1003466
Title:
Software Center Memory/Processor bug
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubunt
Patch that triggers the leak every 1s without the need to actually
install/remove
** Patch added: "repeatedly triggering the "transaction-finished" signal causes
the leak to show"
https://bugs.launchpad.net/ubuntu/+source/software-center/+bug/1003466/+attachment/3169940/+files/trigger-trouble
Anthony pointed me to "python-objgraph": http://mg.pov.lt/objgraph/ that is
also available as a package to do
analysis of what is leaking memory.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1003466
Looking at the pmap out it looks like it the heap growing quite a bit.
Probably releated to cache/db reopen.
However python-apt itself seems to be fine, the following:
from gi.repository import GObject
class GtkMainIterationProgress(apt.progress.base.OpProgress):
"""Progress that just runs th
Install/remove result from htop for the installs:
* 151mb (initial)
* 182mb (powertop)
* 235 (2vcard)
* 250 (4g8)
* 290 (2vcard)
It seems like it matters that they are different.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https:/
** Attachment added: "Terminal ouptput from the for purchase apps, lots of
errors from about line 2500 up"
https://bugs.launchpad.net/ubuntu/+source/software-center/+bug/1003466/+attachment/3159761/+files/terminal-feedback.txt
--
You received this bug notification because you are a member of
** Attachment added: "3 repo applications installed"
https://bugs.launchpad.net/ubuntu/+source/software-center/+bug/1003466/+attachment/3159727/+files/USC4.log
** Description changed:
Bug Description:
Software Centers memory usage increases the more applications you install, to
monitor t
** Attachment added: "Single repo app"
https://bugs.launchpad.net/ubuntu/+source/software-center/+bug/1003466/+attachment/3159714/+files/USC3.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/10034
** Attachment added: "7 paid app installs in the same session"
https://bugs.launchpad.net/ubuntu/+source/software-center/+bug/1003466/+attachment/3159691/+files/USC2.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.
** Description changed:
Bug Description:
- Software Centers memory usage increases the more applications you install, to
monitor this effect I am going to do a single install and the an run with 8
apps and attach the logs to this bug.
+ Software Centers memory usage increases the more applicat
** Attachment added: "USC1.log"
https://bugs.launchpad.net/bugs/1003466/+attachment/3159537/+files/USC1.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1003466
Title:
Software Center Memory/Pro
35 matches
Mail list logo
