Hi there, I'm wondering whether there will be a new release recently? Currently, we take 2.4.0 in our code base. Looking forward to your reply and thank you very much!
Best Regards, Ye Xiaodong *http://R0CKSTAR.zai360.com* <http://R0CKSTAR.zai360.com> ---------- Forwarded message ---------- From: yeahdongcn <yeahdon...@gmail.com> Date: Mon, Jan 23, 2017 at 2:20 PM Subject: When will libsigcplusplus release a new stable one? To: murr...@murrayc.com Hi there, We meet a memory leak at ==83504== 1,600 bytes in 100 blocks are definitely lost in loss record 57 of 62 ==83504== at 0x10000F681: malloc (in /usr/local/Cellar/valgrind/3. 12.0/lib/valgrind/vgpreload_memcheck-amd64-darwin.so) ==83504== by 0x10005E7DD: operator new(unsigned long) (in /usr/lib/libc++.1.dylib) ==83504== by 0x100018F2D: sigc::internal::signal_impl:: insert(std::__1::__list_iterator<sigc::slot_base, void*>, sigc::slot_base const&) (in /usr/local/lib/libsigc-2.0.0.dylib) ==83504== by 0x100000F52: main (signal.h:2667) And here is the sample code, when connecting a list of slots to a signal, there are always memory leaks. // -*- c++ -*- /* Copyright 2002, The libsigc++ Development Team * Assigned to public domain. Use as you wish without restriction. */ #include "testutilities.h" #include <sstream> #include <cstdlib> #include <sigc++/trackable.h> #include <sigc++/signal.h> #include <sigc++/functors/slot.h> #include <sigc++/functors/mem_fun.h> namespace { class my_class { public: sigc::signal<void> destroyed; }; } // end anonymous namespace int main(int argc, char* argv[]) { my_class *c = new my_class(); for (int i = 0; i < 200; i++) { c->destroyed.connect(sigc::slot<void>()); } delete(c); return -1; } We tried the latest stable release 2.6.2, this memory leak still there, so I'm wondering whether there will be a new release recently? Thank you very much! Best wishes, Xiaodong Ye
_______________________________________________ libsigc-list mailing list libsigc-list@gnome.org https://mail.gnome.org/mailman/listinfo/libsigc-list
