[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: 20051010: 6.4.2 pqact memory leak and suggestion

This archive contains answers to questions sent to Unidata support through mid-2025. Note that the archive is no longer being updated. We provide the archive for reference; many of the answers presented here remain technically correct, even if somewhat outdated. For the most up-to-date information on the use of NSF Unidata software and data services, please consult the Software Documentation first.

  • Subject: Re: 20051010: 6.4.2 pqact memory leak and suggestion
  • Date: Tue, 11 Oct 2005 10:07:00 -0600
Daryl,

>Date: Tue, 11 Oct 2005 10:06:53 -0500 (CDT)
>From: Daryl Herzmann <address@hidden>
>Organization: Iowa State University
>To: Steve Emmerson <address@hidden>
>Subject: Re: 20051010: 6.4.2 pqact memory leak and suggestion 

The above message contained the following:

> Good morning,
> 
> Just to follow up, my current memory usage is:
> 
> $ ps auxw | grep pqact
> ldm      12214  0.3 19.5 409076 401480 ?     S    Oct10   4:52 pqact -f 
> ANY-NEXRAD etc/pqact.conf
> ldm      12215  0.2 18.1 406188 373648 ?     S    Oct10   2:40 pqact -f 
> NEXRAD etc/pqact_NEXRAD.conf
> 
> 
> It would appear that it has leveled off, as that was about the memory 
> usage last night.

That's jibes with what I'm seeing here.  I think there's nothing to
worry about (at least regarding a memory-leak in pqact(1) :-).

I've modified pqact(1) so that it prints the decoder command
when appropriate.  The next release will have that "bug-fix".

> My queue size is 400 MB
> 
> daryl
> 
> -- 
> /**
>   * Daryl Herzmann (address@hidden)
>   * Program Assistant -- Iowa Environmental Mesonet
>   * http://mesonet.agron.iastate.edu
>   */

Regards,
Steve Emmerson