Bug 45152 - Make GTK# threadsafe
Summary: Make GTK# threadsafe
Status: NEW
Alias: None
Product: Gtk#
Classification: Mono
Component: gtk-sharp ()
Version: unspecified
Hardware: All All
: --- normal
Target Milestone: ---
Assignee: Bugzilla
Depends on:
Reported: 2016-10-07 08:58 UTC by Timwi
Modified: 2016-10-07 08:59 UTC (History)
2 users (show)

Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.

Please create a new report for Bug 45152 on GitHub or Developer Community if you have new information to add and do not yet see a matching new report.

If the latest results still closely match this report, you can use the original description:

  • Export the original title and description: GitHub Markdown or Developer Community HTML
  • Copy the title and description into the new report. Adjust them to be up-to-date if needed.
  • Add your new information.

In special cases on GitHub you might also want the comments: GitHub Markdown with public comments

Related Links:

Description Timwi 2016-10-07 08:58:03 UTC
It is a common misconception that GTK+ methods can only be called from one “GUI thread”:


Turns out GTK+ has specific mechanisms for thread-safety in it. Using this, the Java bindings for GTK+ (and Gnome) have been made completely thread-safe with a fairly simple tweak:


The CLR (Mono/.NET) Monitor mechanism works exactly the same as Java’s (it is re-entrant and it is highly optimized for the common case in which the current thread already has the lock). Therefore, it stands to reason that making GTK# completely threadsafe should be similarly easy as it apparently was for Java.

The only part that I’m unsure about is whether it is possible (via gdk_threads_set_lock_functions()) to take and release a lock on a CLR object from within native code.