[Gtk-sharp-list] gtk.Application.Invoke memory leak
zeno490 at gmail.com
Sat Nov 19 23:18:44 EST 2011
I updated the bug with the following information:
This is probably caused by bug #731579 I just opened with mono. It
appears an old bug has re-surfaced: marshalling a DynamicMethod with
--debug leaks memory.
Not sure if we want to keep this bug open since it isn't GTK# specific
but it is still affected.
Also, I noticed that Application.Invoke doesn't seem to use a
threadsafe version of g_timeout_add. Is that correct??? Shouldn't it
be using: gdk_threads_add_timeout(...) or using an explicit lock (...)
statement? Application.Invoke is assumed to be used by multi-threaded
applications so this should be important. If it is a bug, I could open
a separate ticket.
Feedback would be welcome on the two points above.
On Tue, Nov 15, 2011 at 1:20 PM, Nicholas Frechette <zeno490 at gmail.com> wrote:
> It'd be nice if we could get a volunteer to try and repro my test case
> on mono/gtk#.
> So we can validate that it isn't a local issue.
> On Mon, Nov 7, 2011 at 5:21 AM, Piotr Budny <piotr.budny at gmail.com> wrote:
>> W dniu 07.11.2011 01:42, Nicholas Frechette pisze:
>>> Bump because I updated the bug with a test case that exhibits the memory leak.
>>> On Wed, Oct 12, 2011 at 11:55 AM, Nicholas Frechette<zeno490 at gmail.com> wrote:
>>>> I created a bug for Application.Invoke leaking timeout proxy handlers.
>>>> Here's the bug's link:
>>>> Just posting here to avoid it getting lost& forgotten like the other
>>>> bugs I filled for mono...
>> Yeah, I really *love* this bug...
>> Gtk-sharp-list maillist - Gtk-sharp-list at lists.ximian.com
More information about the Gtk-sharp-list