mirror of
https://github.com/xcp-ng/xenadmin.git
synced 2024-12-20 23:46:03 +01:00
92f0499911
We observed that some threads can reach deadlock-ish state after they have Invoked into a control's UI thread. When it happens they are all in a waiting for join or in sleep state for very long time, although there should not be any deadlock situations.
It seems this has something to do with multiple parent controls and with which control we invoked on. This should not make a difference, because we have got one UI thread (for MainWindow) they should wait for, but we have seen it does.
The solution that fixed this issue was to invoke on the MainWindow instead of various controls (see
|
||
---|---|---|
.. | ||
CloseXenCenterWarningDialog.cs | ||
CloseXenCenterWarningDialog.Designer.cs | ||
CloseXenCenterWarningDialog.ja.resx | ||
CloseXenCenterWarningDialog.resx | ||
CloseXenCenterWarningDialog.zh-CN.resx | ||
InstallToolsWarningDialog.cs | ||
InstallToolsWarningDialog.Designer.cs | ||
InstallToolsWarningDialog.ja.resx | ||
InstallToolsWarningDialog.resx | ||
InstallToolsWarningDialog.zh-CN.resx | ||
LicenseWarningDialog.cs | ||
LicenseWarningDialog.Designer.cs | ||
LicenseWarningDialog.ja.resx | ||
LicenseWarningDialog.resx | ||
LicenseWarningDialog.zh-CN.resx | ||
LVMoHBAWarningDialog.cs | ||
LVMoHBAWarningDialog.designer.cs | ||
LVMoHBAWarningDialog.ja.resx | ||
LVMoHBAWarningDialog.resx | ||
LVMoHBAWarningDialog.zh-CN.resx | ||
RemoveCrashDumpsWarningDialog.cs | ||
RemoveCrashDumpsWarningDialog.Designer.cs | ||
RemoveCrashDumpsWarningDialog.ja.resx | ||
RemoveCrashDumpsWarningDialog.resx | ||
RemoveCrashDumpsWarningDialog.zh-CN.resx | ||
VcpuWarningDialog.cs | ||
VcpuWarningDialog.Designer.cs | ||
VcpuWarningDialog.ja.resx | ||
VcpuWarningDialog.resx | ||
VcpuWarningDialog.zh-CN.resx |