WebBrowser doesn't like multiple UI threads

dotnet · Jun 19, 2020 · 57f7558 · 57f7558
1 parent a4f4541
commit 57f7558
Show file tree

Hide file tree

Showing 3 changed files with 3 additions and 0 deletions.
diff --git a/...em.Windows.Forms/tests/UnitTests/System/Windows/Forms/AxHost.AxPropertyDescriptorTests.cs b/...em.Windows.Forms/tests/UnitTests/System/Windows/Forms/AxHost.AxPropertyDescriptorTests.cs
@@ -12,6 +12,7 @@
 
 namespace System.Windows.Forms.Tests
 {
+    [Collection("Sequential")] // workaround for WebBrowser control corrupting memory when run on multiple UI threads (instantiated via GUID)
     public class AxHostPropertyDescriptorTests : IClassFixture<ThreadExceptionFixture>
     {
         private const string EmptyClsidString = "00000000-0000-0000-0000-000000000000";

diff --git a/...stem.Windows.Forms/tests/UnitTests/System/Windows/Forms/ControlTests.ControlCollection.cs b/...stem.Windows.Forms/tests/UnitTests/System/Windows/Forms/ControlTests.ControlCollection.cs
@@ -16,6 +16,7 @@
 
 namespace System.Windows.Forms.Tests
 {
+    [Collection("Sequential")] // workaround for WebBrowser control corrupting memory when run on multiple UI threads (instantiated via GUID)
     public class ControlControlCollectionTests : IClassFixture<ThreadExceptionFixture>
     {
         [WinFormsFact]

diff --git a/src/System.Windows.Forms/tests/UnitTests/WebBrowserBaseTests.cs b/src/System.Windows.Forms/tests/UnitTests/WebBrowserBaseTests.cs
@@ -12,6 +12,7 @@ namespace System.Windows.Forms.Tests
 {
     using Size = System.Drawing.Size;
 
+    [Collection("Sequential")] // workaround for WebBrowser control corrupting memory when run on multiple UI threads (instantiated via GUID)
     public class WebBrowserBaseTests
     {
         public static IEnumerable<object[]> Bounds_Set_TestData()