Re: [Boost-bugs] [Boost C++ Libraries] #8079: Chrono memory leak

Subject: Re: [Boost-bugs] [Boost C++ Libraries] #8079: Chrono memory leak
From: Boost C++ Libraries (noreply_at_[hidden])
Date: 2013-03-17 22:42:04

#8079: Chrono memory leak
----------------------------------------------+-----------------------------
  Reporter:  dm413-boost@…                    |       Owner:  viboes 
      Type:  Bugs                             |      Status:  new    
 Milestone:  To Be Determined                 |   Component:  chrono 
   Version:  Boost 1.53.0                     |    Severity:  Problem
Resolution:                                   |    Keywords:         
----------------------------------------------+-----------------------------

Comment (by viboes):

 You are not wrong, there is only one instance.

 Changing all the static members to non-static implies to store a pointer
 to such a single object. Maybe this could be more elegant, but this adds
 an indirection. I would not be against a patch, but currently I have no
 time for such a refactoring.

 Have you checked your suggestion of deleting the allocated memory on the
 destructor in a multi DLL environment?

-- 
Ticket URL: <https://svn.boost.org/trac/boost/ticket/8079#comment:1>
Boost C++ Libraries <http://www.boost.org/>
Boost provides free peer-reviewed portable C++ source libraries.