[Muscle] regarding pcscd daemon that causes memory leak which uses testpcsc.c

Ludovic Rousseau ludovic.rousseau at gmail.com
Mon Feb 4 01:24:33 PST 2008


On Feb 3, 2008 8:12 PM, Sudheer Vemana <sudheervemana at gmail.com> wrote:
> Thanks for your reply , please find the attachment that contains the
> modified code.
>  check hte free memory using top command before executing the applicationad
> and at the time of executiing the code.
>  Please insert and remove the card at the time of application. Please let me
> know how many daemons will actually run.
>  Please give me your valuable suggestions.

I used your sample code but do not notice anything strange.

The free memory reported by top is complex to interpret. If you want
to check the memory used by a process you should use something like:
$ ps axuwww | head -1
to have the name of the columns and:
$ ps axuwww | grep pcscd
to have the values for the pcscd process.
Then check the VSZ (virtual size) column for

In my case the value is stable and changes only when I insert or
remove a reader.

Can you also check the evolution of the pcscd VSZ in your case?

bye

-- 
 Dr. Ludovic Rousseau


More information about the Muscle mailing list