On Tuesday 21 June 2005 01:54, Adeodato Simó wrote:
> * Zack Cerza [Mon, 20 Jun 2005 18:21:31 -0400]:
> > > Anyone else see this?
> >
> > Yep. From top, sorting by "%MEM":
>
> I can't confirm (session running for two days, will keep an eye during
> the week):
>
> PID USER PR NI VIRT RES
On 6/21/05, Zack Cerza <[EMAIL PROTECTED]> wrote:
> On 2005 June 20 Monday 18:29, Ricardo Galli wrote:
> > top is not the right tool to measure memory consumption. OTH the xfree
> > memoryu consuption issue has been clarified several times. One is the top
> > misleading figures, the others is that
On Monday 20 June 2005 07:31 pm, Zack Cerza wrote:
> On 2005 June 20 Monday 18:29, Ricardo Galli wrote:
> > On Tuesday, 21 de June de 2005 00:21, Zack Cerza shaped the electrons to
> >
> > shout:
> > > Yep. From top, sorting by "%MEM":
> > >
> > > PID USER PR NI VIRT RES SHR S %CPU %MEM
On 2005 June 20 Monday 18:29, Ricardo Galli wrote:
> On Tuesday, 21 de June de 2005 00:21, Zack Cerza shaped the electrons to
>
> shout:
> > Yep. From top, sorting by "%MEM":
> >
> > PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+
> > COMMAND
> > 9379 zack 15 0 2202m 409m 8640
* Zack Cerza [Mon, 20 Jun 2005 18:21:31 -0400]:
> > Anyone else see this?
> Yep. From top, sorting by "%MEM":
I can't confirm (session running for two days, will keep an eye during the
week):
PID USER PR NI VIRT RES SHR S %CPU %MEMTIME+ COMMAND
5219 adeodato 16 0 74744 1
On Tuesday, 21 de June de 2005 00:21, Zack Cerza shaped the electrons to
shout:
> Yep. From top, sorting by "%MEM":
>
> PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+
> COMMAND
> 9379 zack 15 0 2202m 409m 8640 S 0.0 40.4 9:31.38 kded
> 9070 root 6 -10 100m 64m 23
On 2005 June 20 Monday 16:49, Ian Eure wrote:
> The 3.4.0 and 3.4.1 packages on alioth seem to have a pretty substantial
> memory leak in kded. Over the course of a week or so of uptime, kded grew
> to eat up over 500mb of memory, and bogged the system down severely. I
> closed /all/ open apps, and
Ian Eure wrote:
> The 3.4.0 and 3.4.1 packages on alioth seem to have a pretty substantial
> memory leak in kded. Over the course of a week or so of uptime, kded grew
> to eat up over 500mb of memory, and bogged the system down severely. I
> closed /all/ open apps, and the size didn't decrease sub
8 matches
Mail list logo