Re: [Opalvoip-devel] Process with PTLIB & OPAL libraries crashes on exit

[Robert J. <ro...@vo...>]

Hmm, I would have thought the memory pool was /never/ destroyed. At 
least not until exiting the application as a whole. I cannot remember 
why the _M_destory() is there, I did not write the original version, and 
it probably stopped some memory leak from being picked up by something.

Bottom line is, I don't care, if you say that this fixes it for you, I 
am happy to include it. I shall direct all future complaints to you! :-)

*Robert Jongbloed*
/OPAL/OpenH323/PTLib Architect and Co-founder./
Commercial support at http://www.voxlucida.com.au

On 9/10/2013 12:31 AM, Юра Чернявский wrote:
> After spend half of my day in gdb & valgrind I got next patch, which 
> solve segmentation fault problem with mt & bitmap allocators:
>
> Index: include/ptlib/object.h
> ===================================================================
> --- include/ptlib/object.h(revision 30632)
> +++ include/ptlib/object.h(working copy)
> @@ -1407,11 +1407,6 @@
>        : __gnu_cxx::__pool<_Thread>(t)
>      {
>      }
> -
> -    ~PMemoryPool() throw()
> -    {
> -      this->_M_destroy();
> -    }
>    };
>    /*Do this template class specialisation so each type has it's own 
> separate
>
> for what reason was called _M_destroy method in PMemoryPool 
> destructor? I can say for sure that with CentOS 6.4 libstdc++ 
> (GLIBCXX_3.4.13) this call cause segmentation fault crash.
>
>