.NET 8.0.21

[dotecxy]

Description

ram 30% (32G) i9-9980HK application No response

Reproduction Steps

No steps, just click button

Expected behavior

normal use

Actual behavior

PresentationCore.dll!System.Windows.Media.Composition.DUCE.Channel.SyncFlush() (IL≈0x000E, Native=0x00007FF9E6266F50+0x72)
PresentationCore.dll!System.Windows.Interop.HwndTarget.UpdateWindowSettings(bool enableRenderTarget, System.Windows.Media.Composition.DUCE.ChannelSet? channelSet) (IL=0x0264, Native=0x00007FF9E5E3FFA0+0x403)
PresentationCore.dll!System.Windows.Interop.HwndTarget.UpdateWindowPos(System.IntPtr lParam) (IL=epilog, Native=0x00007FF9E624A3E0+0x16C)
PresentationCore.dll!System.Windows.Interop.HwndTarget.HandleMessage(MS.Internal.Interop.WindowMessage msg, System.IntPtr wparam, System.IntPtr lparam) (IL≈0x0347, Native=0x00007FF9CC2AF150+0xEB)
PresentationCore.dll!System.Windows.Interop.HwndSource.HwndTargetFilterMessage(System.IntPtr hwnd, int msg, System.IntPtr wParam, System.IntPtr lParam, ref bool handled) (IL=0x0023, Native=0x00007FF9CC2AF0F0+0x35)
WindowsBase.dll!MS.Win32.HwndWrapper.WndProc(System.IntPtr hwnd, int msg, System.IntPtr wParam, System.IntPtr lParam, ref bool handled) (IL=???, Native=0x00007FF9CC25F580+0xBC)
WindowsBase.dll!System.Windows.Threading.ExceptionWrapper.InternalRealCall(System.Delegate callback, object args, int numArgs) (IL=0x0076, Native=0x00007FF9CC2597D0+0x131)
WindowsBase.dll!System.Windows.Threading.ExceptionWrapper.TryCatchWhen(object source, System.Delegate callback, object args, int numArgs, System.Delegate catchHandler) (IL≈0x0002, Native=0x00007FF9CC2596D0+0x32)
WindowsBase.dll!System.Windows.Threading.Dispatcher.LegacyInvokeImpl(System.Windows.Threading.DispatcherPriority priority, System.TimeSpan timeout, System.Delegate method, object args, int numArgs) (IL≈0x00BC, Native=0x00007FF9CC25A120+0x2B9)
WindowsBase.dll!MS.Win32.HwndSubclass.SubclassWndProc(System.IntPtr hwnd, int msg, System.IntPtr wParam, System.IntPtr lParam) (IL≈0x010A, Native=0x00007FF9CC259D30+0x186)
[托管到本机的转换]
WindowsFormsIntegration.dll!System.Windows.Forms.Integration.ElementHost.SetHWndSourceWindowPos() (IL=epilog, Native=0x00007FF9E34D9A90+0x71)
System.Windows.Forms.dll!System.Windows.Forms.NativeWindow.Callback(Windows.Win32.Foundation.HWND hWnd, Windows.Win32.MessageId msg, Windows.Win32.Foundation.WPARAM wparam, Windows.Win32.Foundation.LPARAM lparam) (IL≈0x002A, Native=0x00007FF97BAED240+0x1E1)
[托管到本机的转换]
System.Windows.Forms.dll!System.Windows.Forms.Control.SetVisibleCore(bool value) (IL≈0x0000, Native=0x00007FF97C741CC0+0x13D)

Regression?

No response

Known Workarounds

No response

Impact

No response

Configuration

No response

Other information

No response

[dotecxy]

app.exe_260508_144534.dmp.zip

[dotecxy]

[lindexi]

@dotecxy From your dump file, we can find that it is waitting hSyncFlushEvent in connection.cpp:

wpf/src/Microsoft.DotNet.Wpf/src/WpfGfx/core/uce/connection.cpp

Lines 344 to 347 in 7f005fa

	IFCW32X(dwWaitResult,
	WAIT_FAILED, // failureCode
	::WaitForSingleObject(masterEntry.hSyncFlushEvent, INFINITE)
	);

May be the CMilServerChannel::SignalFinishedFlush not be called.

Maybe effect by D:\Program files\sinsam\app\bin\VZDirectorSdk.dll 、D:\Program files\sinsam\app\bin\DeviceCapture\DeviceCaptureClient.dll . Could you remove it?

[dotecxy]

@dotecxy从你的转储文件中，我们可以看到它正在hSyncFlushEventconnection.cpp 中等待：

wpf/src/Microsoft.DotNet.Wpf/src/WpfGfx/core/uce/connection.cpp

第 344 行至 347 行 7f005fa

IFCW32X（dwWaitResult，
WAIT_FAILED，//失败代码
::WaitForSingleObject (masterEntry.hSyncFlushEvent, INFINITE)
）；
可能CMilServerChannel::SignalFinishedFlush不会被叫到。

可能是受D:\Program files\sinsam\app\bin\VZDirectorSdk.dll……影响D:\Program files\sinsam\app\bin\DeviceCapture\DeviceCaptureClient.dll。你能把它移除吗？

I cannot remove them because they are core C++libraries

[lindexi]

@dotecxy How about the demo?

再写一个 demo 呢？只干掉这两个 dll 测试一下效果。如果没有问题，则证明这两个 dll 才是导致问题的原因。由于 DUMP 是事后现场，不知道过程发生了什么事情，导致无法继续渲染。先做一些实验测试，进度应该会更快

[dotecxy]

@lindexi 感谢提供建议，请教下是如何看出是这两个dll导致的问题

[lindexi]

@dotecxy 我没有多少明确的证据可以猜测（对，还不是证明）是这两个 DLL 导致的，只能说猜测可能与之相关，就想来做做实验。因为我感觉实验成本比调试成本应该会低很多，仅仅如此而已

猜测的理由是： 卡住的地方证明了渲染服务端还没完成，为什么没完成呢？猜测可能是渲染过程被打断，猜测可能是显卡问题，猜测可能是渲染层可能相关的问题。于是就在猜相关的 DLL 可能的影响，然后就猜这两个 DLL 也许相关

首先 Channel.SyncFlush 卡住，这和 C# dotnet 层无关，本质是 WaitForSingleObject(masterEntry.hSyncFlushEvent, INFINITE) 卡住，进一步调查 hSyncFlushEvent 的引用又可以知道，预期行为是渲染完成之后就会进入 Set 模式（完成等待），但这里没有，那就可能是渲染服务端没完成。渲染服务端没完成就可以继续按照上文的方式猜测