On 7/2/2018 8:40 AM, Alexander Grund via Boost wrote:
Although crashing is not observed with the slightly older Boost releases (e.g. 1.66, 1.65.1, 1.64, etc.), intentionally isolating Boost.Serialization as Gavin describes fails, with the already described lack of destructor invocations and memory leak. Did you test the code I sent around with static boost and those versions?
No, I have not tested the 1.68 revision. If my day goes well enough with my primary tasks, I will build 1.68 early this evening or possibly July 5th. This will be strictly on Windows with both Microsoft 15.6.4 and Intel C++ 18.0, Update 3. --Robert I expect a crash in 1.68 (if the commit is not reverted) and
in 1.65.x, so if you don't experience one I'd be interested in details (OS, stdlib, compiler etc.). Also: 1.64 should be fine and 1.65 should not leak, but crash. 1.66/1.67 have the leak.
Alex
_______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost