You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
[Win32] Spin event loop in Edge instead of only processing OS messages
Before recent improvements of the Edge implementation, capabilities of
to deal with asynchronous disposals of the browser were missing, leading
to unhandled errors inside the WebView initialization. They have been
worked around by not processing all kinds of asynchronously scheduled
events (like a disposal) but only those being processes by the OS event
queue. This was still necessary to process the OS callbacks for WebView
initialization and other operations.
In some cases, this may lead to an Edge browser instance blocking the UI
thread, as some asynchronously scheduled tasks need to be processed but
are not. In addition, enhancements of the Edge implementation made it
capable of processing asynchronous browser display disposals.
This change simplifies the event processing inside Edge to not just
process the next OS message but to just ordinarily spin the event loop.
Copy file name to clipboardexpand all lines: tests/org.eclipse.swt.tests/JUnit Tests/org/eclipse/swt/tests/junit/Test_org_eclipse_swt_browser_Browser.java
+9-3
Original file line number
Diff line number
Diff line change
@@ -302,11 +302,17 @@ private int reportOpenedDescriptors() {
0 commit comments