Any known memory leak issues in handling SIGEV threads in Linux?
Sowmya Sridharan
sowmya.sridharan at tcs.com
Thu Feb 10 01:06:28 EST 2011
Hi All,
In a stable system with 2.6.14 kernel, which continuously sends/receive
packets, I noticed an increase in slab size of around 1.5GB in 30 hours.
I see a continuous increase in number of task_struct and size-16384(thread
info) object.
I use an application that uses SIGEV timer thread with time-out of 20
millisecs. Each time, upon expiry of SIGEV timer(20 millisecs), a thread
start routine will run "as if" it were a new thread, to process the
packets in the system.
Whenever the application is killed/restarted, all the task_struct objects
are getting released.
1. Is there any known issue in 2.6.14 kernel for handling SIGEV timer
thread ?
2.Will there be any issue in 2.6.14 kernel, in clean up of task_struct for
application that creates/deletes threads at a rate of 20 millisec?
Thread creation/deletion are handled properly in the application. Still I
am unable to figure out reason for memory leak.
Appreciate your inputs.
Thanks,
Sowmya
=====-----=====-----=====
Notice: The information contained in this e-mail
message and/or attachments to it may contain
confidential or privileged information. If you are
not the intended recipient, any dissemination, use,
review, distribution, printing or copying of the
information contained in this e-mail message
and/or attachments to it are strictly prohibited. If
you have received this communication in error,
please notify us by reply e-mail or telephone and
immediately and permanently delete the message
and any attachments. Thank you
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20110210/3e575890/attachment.html
More information about the Kernelnewbies
mailing list