[Webkit-unassigned] [Bug 72589] [GTK] Expose accessibility hierarchy in WebKit2 to ATK/AT-SPI based ATs

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Wed Jan 4 03:52:19 PST 2012


--- Comment #14 from Carlos Garcia Campos <cgarcia at igalia.com>  2012-01-04 03:52:19 PST ---
(In reply to comment #13)
> (In reply to comment #12)
> > [...]
> > If you need to block, why don't use g_spawn_sync() instead of the async version?
> Because I need to block in a way that I need to wait for the child to send me an "OK" message when it's ready but, at the same time, I don't want to wait forever in case something goes wrong in the child process (imagine it hangs for some reason), so I need to be able to unblock if a certain amount of time (a timeout) has happened before getting such a response, which is something I can't specify with g_spawn_sync() I think.
> So, that's why I used g_spawn_async() instead: to have more control over the whole thing in a way g_spawn_sync() wouldn't allow. Anyway, according to docs, g_spawn_sync() "calls g_spawn_async_with_pipes() internally" :-)
> Anyway, if there's a way to handle that timeout without having to do this manually, I'd be glad to know of it and more than happy to change the implementation of this part, of course.

static bool kChildFinished = true;

G_GNUC_NORETURN static gpointer timeoutMonitor(gpointer)
        g_usleep(kMaxWaitForChild * G_USEC_PER_SEC);

        if (kChildFinished)

        exit (0);

static void timeoutMonitorStart()
        kChildFinished = false;
#if (!GLIB_CHECK_VERSION(2,31,0))
        g_thread_create(timeoutMonitor, 0, FALSE, 0);
         g_thread_new("TimeoutMonitor", timeoutMonitor, 0);

static void timeoutMonitorStop()
     kChildFinished = true;



Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

More information about the webkit-unassigned mailing list