|
From: gnome-perl (bugzilla.gnome.org) <bug...@bu...> - 2008-01-06 06:30:36
|
If you have any questions why you received this email, please see the text at the end of this email. Replies to this email are NOT read, please see the text at the end of this email. You can add comments to this bug at: http://bugzilla.gnome.org/show_bug.cgi?id=507610 gnome-perl | Gtk2::GladeXML | Ver: unspecified muppet changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |sc...@as... Status|UNCONFIRMED |RESOLVED Resolution| |NOTABUG ------- Comment #1 from muppet 2008-01-06 06:30 UTC ------- If you add the line die "Failed to enable thread safety" unless Glib::Object->set_threadsafe (1); immediately after the "use Glib;" line (specifically, before any calls to Glib or Gtk2 or related packages), then your example script no longer crashes. Instead, i see a "Scalars leaked: 1" message at the close of each thread, which is, i believe, related to the fact that the object is being kept alive by the object tracking. Please see: "Can I use threads with gtk2-perl" entry in FAQ (predates object tracking) http://live.gnome.org/GTK2-Perl/FrequentlyAskedQuestions#head-4d5ea9310685f66fc167cf8497357e341f73128b Glib::Object::set_threadsafe() http://gtk2-perl.sourceforge.net/doc/pod/Glib/Object.html#boolean_Glib_Object_ "gtk2-perl thread safe" mailing list announcement http://mail.gnome.org/archives/gtk-perl-list/2004-May/msg00094.html zentara has a decent summary of how to do thread-safety here: http://objectmix.com/perl/19619-perl-s-gui-2.html#post63228 If that doesn't fix your problem, please reopen. -- See http://bugzilla.gnome.org/page.cgi?id=email.html for more info about why you received this email, why you can't respond via email, how to stop receiving emails (or reduce the number you receive), and how to contact someone if you are having problems with the system. You can add comments to this bug at http://bugzilla.gnome.org/show_bug.cgi?id=507610. |