pthread_mutex and process termination

Question

Before using a pthread_mutex_t pthread_mutex_init() should be called, and after it's not longer required it should be destroyed using pthread_mutex_destroy().

My question is, what happens if my process terminates before it can call pthread_mutex_destroy(), for example a SIGKILL, SIGINT or SIGABORT? Is it possible that some resource will leak?

Same question goes to pthread_cond_init/destroy as well.

Why do you think there can be a resource problem? A mutex is just a data structure in user space. When the process terminates, all memory is given back to the OS. — Alain Merigot, Mar 04 '19 at 00:09
Your process or a thread? Because when the process terminates all threads finish and the resources are freed. — Horacio Goetendia, Mar 04 '19 at 00:15
@AlainMerigot, that's kind of answer I was looking for, just wanted to be sure. — Alberto Pires, Mar 04 '19 at 00:21

score 3 · Accepted Answer · answered Mar 04 '19 at 02:07

Not on any platform you're likely to use. Objects like mutexes and condition variables are just chunks of memory in the process' address space. When a process terminates, its address space ceases to exist. So it's not possible for any resources to leak.

Process-shared resources are more complex. While the resources won't leak, they may still exist and may even still be in use by other processes.

pthread_mutex and process termination

1 Answers1