Memory leak issue in reset() function from boost::thread_specific_ptr

Open
#371 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
38/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
cpp

Research direction

Start with the minimal program in the issue and run the supplied Valgrind command to reproduce the report. Trace boost::thread_specific_ptr::reset() through the thread-specific storage functions named in the leak stack. Done means the reported allocation is no longer leaked while the reset() example continues to behave correctly.

Written by the indexing model from the issue text.

Description

Following memory leak issue is observed with reset() method from boost::thread_specific_ptr by using valgrind tool in Boost 1.75.

### Leak description:

==27891== 24 bytes in 1 blocks are still reachable in loss record 1 of 2
==27891==    at 0x4835DEF: operator new(unsigned long) (in /usr/lib/x86_64-linux-gnu/valgrind/vgpreload_memcheck-amd64-linux.so)
==27891==    by 0x113064: boost::detail::make_external_thread_data() (in /home/{user}/boost_1_75_0/a.out)
==27891==    by 0x114084: boost::detail::add_new_tss_node(void const*, void (*)(void (*)(void*), void*), void (*)(void*), void*) (in /home/{user}/boost_1_75_0/a.out)
==27891==    by 0x1102F5: boost::thread_specific_ptr<int>::reset(int*) (in /home/{user}/boost_1_75_0/a.out)
==27891==    by 0x10DC07: main (in /home/{user}/boost_1_75_0/a.out)

Code Snippet:

#include <boost/thread.hpp>
#include <iostream>
int main()
{
	boost::thread_specific_ptr<int> conv_thread_ptr;
	if(!conv_thread_ptr.get())
	{
        	conv_thread_ptr.reset(new int);
	}
	return 0;
}

Command used for compilation:
g++ main.cpp -I./boost_1_75_0_install/include ./boost_1_75_0_install/lib/libboost_thread.a -lpthread

Command used for memory leak checking with valgrind:
valgrind --leak-check=full --show-leak-kinds=all --track-origins=yes --verbose --log-file=valgrind-out.txt ./a.out

@vaishnavkatiyar

Dominant language
C++
Stars
213
Forks
171
PR merge metrics
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from boostorg/thread

All issues in boostorg/thread

Similar issues

More C++ issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.