After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 337991 - G_IO_OUT is not triggered when registered in timeout event handler
G_IO_OUT is not triggered when registered in timeout event handler
Status: RESOLVED DUPLICATE of bug 331214
Product: glib
Classification: Platform
Component: win32
2.8.x
Other Windows
: Normal minor
: ---
Assigned To: gtk-win32 maintainers
gtk-win32 maintainers
Depends on:
Blocks:
 
 
Reported: 2006-04-10 18:03 UTC by Armin Burgmeier
Modified: 2006-04-11 14:45 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Simple testcase (1.18 KB, text/plain)
2006-04-10 18:04 UTC, Armin Burgmeier
Details

Description Armin Burgmeier 2006-04-10 18:03:43 UTC
When calling g_io_add_watch watching for G_IO_OUT on a socket in a timeout event handler the IO_OUT event is not triggered until the next wakeup of the main event loop. The problem can easily be workarounded by adding an idle watch after having called g_io_add_watch. The problem does only occur on my Windows XP based system, not on the GNU/Linux one.

I originally registered this issue in a GTK+ based application where a single mouse motion event caused the IO_OUT to be triggered, so I guess it is enough to wake up the main loop (as the idle workaround does). The problem could be reproduced with Glib 2.8.x and Glib CVS HEAD.

A simple testcase to reproduce the problem is attached to this bug report. I left out error checking to keep the example small and simple.
Comment 1 Armin Burgmeier 2006-04-10 18:04:58 UTC
Created attachment 63175 [details]
Simple testcase
Comment 2 Dominic Lachowicz 2006-04-11 14:45:44 UTC
This looks a lot like bug 331214

*** This bug has been marked as a duplicate of 331214 ***