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
I run screenrecorderlib latest version as a part of my application but my application runs automated in a vm as a cloudtest and in such remote runs i see that screenrecorderlib consistently crashes due to invalid pointer read.
I do not have the logs for screenrecorderlib even though i have log enabled, probably because the crash happens before any file is written. ( This probably also might be helpful - as in write logs as and when they are available)
When i log into the vm and run my application manually everything works as expected and i do not have any more information other than the dump below. Could this be because the vm run does not have any displays or monitors?
If the software runs as a Windows service, and not a desktop program. If it runs as a service, all access to the video output is blocked by Windows for security reasons. Virtual monitors should work just fine, as long as it is run in the virtual desktop. The caveat is that if you remote in to the VM with remote desktop, and then closes the connection, the virtual monitor is uninstalled and the recording stops. A running VM with nobody remoting in is thus regarded as having no video output as far as i know, and not recordable.
I run screenrecorderlib latest version as a part of my application but my application runs automated in a vm as a cloudtest and in such remote runs i see that screenrecorderlib consistently crashes due to invalid pointer read.
I do not have the logs for screenrecorderlib even though i have log enabled, probably because the crash happens before any file is written. ( This probably also might be helpful - as in write logs as and when they are available)
When i log into the vm and run my application manually everything works as expected and i do not have any more information other than the dump below. Could this be because the vm run does not have any displays or monitors?
msvcp140!mtx_do_lock+0x74 [f:\dd\vctools\crt\crtw32\stdcpp\thr\mutex.c @ 99]
screenrecorderlib!Concurrency::task_completion_event_unsigned char_::set+0x63 [C:\Program Files\Microsoft Visual Studio\2022\Enterprise\VC\Tools\MSVC\14.40.33807\include\ppltasks.h @ 2441]
screenrecorderlib!Concurrency::task_from_result+0xd9 [C:\Program Files\Microsoft Visual Studio\2022\Enterprise\VC\Tools\MSVC\14.40.33807\include\ppltasks.h @ 7076]
screenrecorderlib!std::make_unique_RecordingManager::TaskWrapper,0_+0x5a [C:\Program Files\Microsoft Visual Studio\2022\Enterprise\VC\Tools\MSVC\14.40.33807\include\memory @ 3595]
screenrecorderlib!RecordingManager::RecordingManager+0x35 [C:__w\1\s\library\ScreenRecorderLib\ScreenRecorderLibNative\RecordingManager.cpp @ 69]
presentationcore!DomainBoundILStubClass.IL_STUB_PInvoke+0x6e
screenrecorderlib!ScreenRecorderLib::Recorder::Recorder+0xb1
screenrecorderlib!ScreenRecorderLib::Recorder::CreateRecorder+0x26
The text was updated successfully, but these errors were encountered: