On Tue, Feb 2, 2010 at 4:36 PM, Carlos Galisteo <cgalis...@k-rolus.net> wrote: > On Tue, Feb 2, 2010 at 6:43 AM, Roger <wen...@gmail.com> wrote: > >> * http proxy set >> * update interval: 30s >> * refresh search results > > Are you using http or https connections?
I'm using http and the service API is twitter.com, no specific settings here. > >> I kept it open for about 2 hours and a suspend/resume happened during >> that time (not sure whether suspend/resume has anything to do with >> this) > > I didn't try to suspend/resume. Good point. > >> memory consumption shown in 'top': >> begin: VIRT 200+m, RES 80+m >> after 2hrs: VIRT 449m, RES 326m and still climbing > > That's much more than my own results. I'll do some more tests. Is there any tips/tools with which I could locate the possible bug here? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
