[Webkit-unassigned] [Bug 234748] New: [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
Thu Dec 30 03:12:20 PST 2021


https://bugs.webkit.org/show_bug.cgi?id=234748

            Bug ID: 234748
           Summary: [GTK] (.NET Bindings) - Initializing WebKitGTK seems
                    to cause new .Net Processes to never exit again
           Product: WebKit
           Version: Other
          Hardware: PC
                OS: Linux
            Status: NEW
          Keywords: Gtk
          Severity: Normal
          Priority: P3
         Component: WebKitGTK
          Assignee: webkit-unassigned at lists.webkit.org
          Reporter: v.m.vollers at gmail.com
                CC: bugs-noreply at webkitgtk.org

Overview: 

I think there is an underlying issue with WebKitGTK and its interaction with currently existing .NET bindings on Linux. This is quite hard to pinpoint exactly and I hope someone here can verify this behavior and perhaps find a solution.

The moment an embedded WebKitGTK component / window is initialized, newly created Processes (new System.Diagnostics.Process) will never "exit". The reason I believe it might have something to do with WebKitGTK and the reason I'm filing a bug here is that the same happens with multiple/different bindings.

For example https://github.com/tryphotino/photino.NET , https://github.com/JBildstein/SpiderEye and https://github.com/GtkSharp/GtkSharp .

The common denominator seems to be they all use WebKitGTK as an embedded browser engine for Linux.


Steps to Reproduce: 

I've created several minimal sample applications for different bindings in this github issue: https://github.com/tryphotino/photino.NET/issues/74

All these sample applications do is run the test at the start (create a new process, run, wait for exit) and again after a WebKitGTK window has been initialized and destroyed.


Actual Results: 

The first test succeeds (the new process runs and exits). However, after a WebKitGTK window/component has been created, the second test fails. (it now keeps waiting on Process.WaitForExit)


Expected Results: 

Both tests to start a new process and exit normally.


Build Date & Hardware: 

The build underlying "apt-get install libgtk-3-dev libwebkit2gtk-4.0-dev" on 26 December 2021 on Ubuntu 20.10


Additional Builds and Platforms: 

Under other browser engines (on windows: WebView2 - Edge Chromium) it works as expected.

-- 
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/20211230/40906e15/attachment-0001.htm>


More information about the webkit-unassigned mailing list