Dear Mustafa, I just filed http://bugzilla.qooxdoo.org/show_bug.cgi?id=9166
I did not create a PR since fixing it should be as simple as calling dispose(). Regards, -- George Nikolaidis (gnikolai...@ergobyte.gr) MEng, MSc Information Systems ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Ergobyte Informatics S.A. Innovative Software Development 21 Aristotelous str., 54624 Thessaloniki, Greece Tel: +302310288434, Fax: +302310288134 Website:www.ergobyte.gr On 12/06/2015 12:44 μμ, Mustafa Sak wrote: > Hi George, > > many thanks for reporting that issue. Would you like to open a bug please? > Feel free to send us a pull request, if you already fixed that issue. > > Dank & Gruß > Mustafa Sak > Softwareentwickler > Mail Development > 1&1 Mail & Media Development & Technology GmbH | Brauerstraße 48 | 76135 > Karlsruhe | Germany > Phone: +49 721 91374-6977 > E-Mail: mustafa....@1und1.de | Web: www.1und1.de > > > -----Ursprüngliche Nachricht----- > Von: George Nikolaidis [mailto:gnikolai...@ergobyte.gr] > Gesendet: Donnerstag, 11. Juni 2015 13:43 > An: qooxdoo-devel@lists.sourceforge.net > Betreff: [qooxdoo-devel] qx.event.message.Bus.dispatchByName() does not > dispose its message > > Dear all, > > While browsing the QX codebase, I discovered what I consider an important > memory leak; it seems that while > qx.event.message.Bus.dispatchByName() creates a new qx.event.message.Message > object, it does not trouble itself with disposing it after usage. > > Since qx.event.message.Message extends qx.core.Object and calls the base > constructor which registers every instance in the registry, I believe this > leads to memory leaks. > > Please confirm so that I file a bug report, > > Best regards, > > ------------------------------------------------------------------------------ _______________________________________________ qooxdoo-devel mailing list qooxdoo-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
