From: gnome-perl (bugzilla.gnome.o. <bug...@gn...> - 2013-11-11 12:56:28
|
https://bugzilla.gnome.org/show_bug.cgi?id=711839 gnome-perl | Glib | unspecified Summary: Add Glib::MainContext::invoke() wrapper Classification: Bindings Product: gnome-perl Version: unspecified OS/Version: All Status: NEW Severity: normal Priority: Normal Component: Glib AssignedTo: gtk...@li... ReportedBy: eb...@gm... QAContact: gtk...@li... GNOME version: --- We should have this in the bindings. See the commit log for more information. -- Configure bugmail: https://bugzilla.gnome.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug. You are the assignee for the bug. |
From: gnome-perl (bugzilla.gnome.o. <bug...@gn...> - 2013-11-11 12:56:34
|
https://bugzilla.gnome.org/show_bug.cgi?id=711839 gnome-perl | Glib | unspecified --- Comment #1 from Emmanuele Bassi (:ebassi) <eb...@gm...> 2013-11-11 12:56:22 UTC --- Created an attachment (id=259554) View: https://bugzilla.gnome.org/attachment.cgi?id=259554 Review: https://bugzilla.gnome.org/review?bug=711839&attachment=259554 Add Glib::MainContext::invoke() wrapper Modern GLib is trying to phase out GMainLoop in favour of GMainContext, especially when it comes to threads usage. The invoke() method of GMainContext is used in two cases: • if the code is using (native) threads with multiple main contexts and wishes to invoke a callback function in the correct context, which is the case with GIO • if the code is using an API that explicitly breaks when used from multiple threads, and requires that each callback is invoked a specific main context, which is the case of GTK+ The usual way to perform this operation before the introduction of the g_main_context_invoke() function was to schedule an idle source; this requires setting up idle sources for specific contexts (thus foregoing all the convenience API). Given that the documentation for the libraries based on GLib is starting to point in the direction of g_main_context_invoke(), the Perl bindins should provide a wrapper for this function. -- Configure bugmail: https://bugzilla.gnome.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug. You are the assignee for the bug. |
From: gnome-perl (bugzilla.gnome.o. <bug...@gn...> - 2013-12-08 17:31:12
|
https://bugzilla.gnome.org/show_bug.cgi?id=711839 gnome-perl | Glib | unspecified Torsten Schoenfeld <kaffeetisch> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |kaf...@gm... --- Comment #2 from Torsten Schoenfeld <kaf...@gm...> 2013-12-08 17:31:00 UTC --- The patch looks good to me (apart from some minor spaces-vs-tabs issues), but it needs some unit tests. Also, as far as I can see, this would suffer from the same kinds of problems that the Glib::Idle approach has when used by Perl code running in different threads: If you call $context->invoke() from some thread on a context not attached to that thread, then gperl_main_context_invoke_callback() will access SV* pointers from the calling thread in the context's thread, i.e. it will try to use SV* pointers belonging to one Perl interpreter instance with another Perl interpreter instance. This is unreliable. This is not an argument against the patch, however. -- Configure bugmail: https://bugzilla.gnome.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug. You are the assignee for the bug. |
From: gnome-perl (G. B. <bug...@gn...> - 2015-12-06 01:07:35
|
https://bugzilla.gnome.org/show_bug.cgi?id=711839 Shae Johnson <DSh...@gm...> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |DSh...@gm... -- You are receiving this mail because: You are the QA Contact for the bug. You are the assignee for the bug. |
From: gnome-perl (G. B. <bug...@gn...> - 2021-07-05 12:22:40
|
https://bugzilla.gnome.org/show_bug.cgi?id=711839 GNOME Infrastructure Team <gno...@gn...> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED CC| |gno...@gn... Resolution|--- |OBSOLETE --- Comment #3 from GNOME Infrastructure Team <gno...@gn...> --- GNOME is going to shut down bugzilla.gnome.org in favor of gitlab.gnome.org. As part of that, we are mass-closing older open tickets in bugzilla.gnome.org which have not seen updates for a longer time (resources are unfortunately quite limited so not every ticket can get handled). If you can still reproduce the situation described in this ticket in a recent and supported software version, then please follow https://wiki.gnome.org/GettingInTouch/BugReportingGuidelines and create a new ticket at https://gitlab.gnome.org/GNOME?utf8=%E2%9C%93&filter=perl- Thank you for your understanding and your help. -- You are receiving this mail because: You are the QA Contact for the bug. You are the assignee for the bug. |