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
{{ message }}
This repository was archived by the owner on Dec 4, 2021. It is now read-only.
To test on Windows 10, COMGLB_FAST_RUNDOWN is set on client side. It would be interesting to test if this affects the rundown time on Windows 10. If not, does it help enabling it on Player side?
Test how COMGLB_FAST_RUNDOWN affects time to call FinalRelease on server created objects in the Client address space after a server crash.
See branch https://github.com/jogerh/UnstructuredCom/tree/GarbageCollectionDemo
https://github.com/jogerh/UnstructuredCom/tree/GarbageCollectionDemo now shows a dialog after 5-15 minutes saying that Frame::FinalRelease was called on Windows 7. This demonstrates the delayed cleanup of COM objects after server crash.
To test on Windows 10, COMGLB_FAST_RUNDOWN is set on client side. It would be interesting to test if this affects the rundown time on Windows 10. If not, does it help enabling it on Player side?