开发者

posix timer_create() function causing memory leak on linux

开发者 https://www.devze.com 2023-01-24 18:39 出处:网络
I am using timer_create function for timer functionality in my application. When timeout happens, a new thread gets created. That time my application\'s memory usage is getting increased by around 11m

I am using timer_create function for timer functionality in my application. When timeout happens, a new thread gets created. That time my application's memory usage is getting increased by around 11mb. I also have 开发者_如何学Goset the thread attribute to PTHREAD_CREATE_DETACHED. Any help is appreciated. I also want to know how long will the thread that gets created when timeout happens be alive?


Valgrind is an invaluable tool for finding memory leaks in a Linux environment


I doubt it has anything to do with your timer.

If you create a new thread, the thread needs space for the stack. As far as I know this memory gets allocated once at thread creation because it has to be contiguous.

That may sound like a lot of wasted memory, but it is not. First off, you can lower the stack size if you want, second: Only the address-space inside your process gets allocated. Physical memory only gets allocated if you use the stack.


This question makes no sense without the code.

timer_create does not make a thread by itself. Your code must be making the thread.

Your memory leak is almost certainly caused by something wrong in your code. Since we can't see your code we can't help solve the problem.


Any thread stays "active" until you exit its thread function. Your leak is most probably the thread's stack - that will not go away until you invoke thread_join or some such.


Too few info given, but maybe helps:
Periodic Timer Overrun and Resource Allocation

0

精彩评论

暂无评论...
验证码 换一张
取 消

关注公众号