2017 R2 SDK(32 Bit) intermittent error

MIP
, ,
1

2017 R2 SDK (32 bit ).

On certain machines we seem to have an intermittent issue where by we receive an error

FirstChanceException: at VideoOS.Toolkit.RendererToolkit.RemoveSources(ISet`1 sourcesToRemove) !!! inner External component has thrown an exception.

FirstChanceException: at VideoOS.Toolkit.RendererToolkit.RemoveSources(ISet`1 sourcesToRemove) !!! inner class NmError::CmError: Error initialize render buffer surface!

This seems to be during creation / disposal of an ImageViewerControl instance obtained by calling ClientControl.Instance.GenerateImageViewerControl();

This problem seems to be particularly apparent after unlocking a screen saver on the affected workstations and seems to result in a fatal exception reported in the application event logs with the source typically being an exit code 0xc0000005 with FaultingModule as CoreToolkits.dll.

Is this a known issue and if so are there any workarounds available to mitigate the impact ?

Is there any specific analysis such as crash dump logs etc that might prove useful in diagnosing a cause ?

Best regards,

Damien.

2

Additional info obtained from the affected customer pc as follows

ee the end of this message for details on invoking

just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************

VideoOS.Toolkit.StdCppException: class NmError::CmError: Error initialize render buffer surface!

at VideoOS.Toolkit.RendererToolkit.RemoveSources(ISet`1 sourcesToRemove)

at VideoOS.UI.Common.WPF.VideoPlayer.Toolkit.ToolkitWrapper.ExecuteSourceOperation(ISourceOperation sourceOperation)

at VideoOS.UI.Common.WPF.VideoPlayer.Toolkit.VideoImage.VideoImageManager.VideoImageClose(VideoImage videoImage)

at VideoOS.UI.Common.WPF.VideoPlayer.Toolkit.VideoImage.VideoImage.Close()

at VideoOS.UI.Common.WPF.VideoPlayer.Toolkit.ToolkitVideoSource.Disconnect()

at VideoOS.UI.Common.WPF.VideoPlayer.Toolkit.ToolkitVideoSource.Connect(XmlDocument configurationXml, XmlDocument digitalZoomConfigurationXml, List`1 renderingParameters, Boolean multicast)

at VideoOS.UI.Common.WPF.VideoPlayer.VideoPlayer.Connect(XmlDocument configurationXml, XmlDocument digitalZoomConfigurationXml, List`1 renderingParameters, String cameraName, String cameraAddress, Boolean multicast)

at VideoOS.Platform.SDK.UI.DirectX.ImageViewerDirectX.ConnectUsingCameraConfigurationXml(String bstrUsername, String bstrPassword, String bstrCameraConfigurationXml)

at VideoOS.Platform.SDK.UI.SDKImageViewerControl.ConnectToServer()

at VideoOS.Platform.SDK.UI.SDKImageViewerControl.ReconnectTimer_Tick(Object obj, EventArgs e)

at System.Windows.Forms.Timer.OnTick(EventArgs e)

at System.Windows.Forms.Timer.TimerNativeWindow.WndProc(Message& m)

at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

This seems to affect only some of the clients and it is possibly ones that are using KVM extenders to present the PC monitors as a Video Wall. As such I am trying to clarify if this might occur as the result of a hardware glitch in the KVM resulting in a momentary monitor disconnect event or something like this in the PC.

3

A lot of issues with Smart Client crashes experienced after introduction of hardware acceleration are very simply solved by an upgrade of the PC graphics drivers. Please try this.

If you still experience the crash..

For me it would be interesting to know if you run the 32 bit Smart Client and enable the diagnostics overlay, does it show that hardware acceleration is being used?

Does the 32 bit Smart Client crash in the same way? Might not be easy to test if you see this very intermittinet and in general use you client instead, but if you have a test let me know..