[Webkit-unassigned] [Bug 234748] [GTK] (.NET Bindings) - Initializing WebKitGTK seems to cause new .Net Processes to never exit again

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Sat Jan 8 04:35:51 PST 2022


--- Comment #4 from Vincent Vollers <v.m.vollers at gmail.com> ---
The problem is fixed using a workaround in one of the libraries in the following pull request: https://github.com/tryphotino/photino.Native/pull/77

The underlying issue seems to be that webkit or gtk at some point changes the signal handling for SIGCHLD which stops other processes later on from receiving this signal. Thus causing the behavior as described.

The workaround is to save the original action in the binding library before calling certain webkit functions

struct sigaction old_action;
sigaction (SIGCHLD, NULL, &old_action);
sigaction (SIGCHLD, &old_action, NULL);

The original discussion and proposed workaround which solved this for me came from another project

I'm not sure where the actual solution would be, but perhaps this will help someone track down the actual underlying issue.

You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-unassigned/attachments/20220108/14d649cc/attachment.htm>

More information about the webkit-unassigned mailing list