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. Thanks, Nicholas On Tue, Nov 15, 2011 at 1:20 PM, Nicholas Frechette <[email protected]> wrote: > Hi, > 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. > > Nicholas > > On Mon, Nov 7, 2011 at 5:21 AM, Piotr Budny <[email protected]> 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<[email protected]> >>> wrote: >>>> Hi, >>>> I created a bug for Application.Invoke leaking timeout proxy handlers. >>>> Here's the bug's link: >>>> https://bugzilla.novell.com/show_bug.cgi?id=723148 >>>> >>>> Just posting here to avoid it getting lost& forgotten like the other >>>> bugs I filled for mono... >>>> Cheers, >>>> Nicholas >> >> Yeah, I really *love* this bug... >> >> vip; >> >> _______________________________________________ >> Gtk-sharp-list maillist - [email protected] >> http://lists.ximian.com/mailman/listinfo/gtk-sharp-list >> > _______________________________________________ Gtk-sharp-list maillist - [email protected] http://lists.ximian.com/mailman/listinfo/gtk-sharp-list
