Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Setting f200_laser_power on started device results in hang #303

Closed
tasptz opened this issue Oct 3, 2016 · 2 comments
Closed

Setting f200_laser_power on started device results in hang #303

tasptz opened this issue Oct 3, 2016 · 2 comments
Labels

Comments

@tasptz
Copy link

tasptz commented Oct 3, 2016

When I try to set f200_laser_power it sometimes causes my program to hang, as it does not return from the set_option call. Is this a bug or is it not intended/allowed to set this option on a started device?

Required Info
Camera Model SR300
Firmware Version 3.17.0.0
Operating System & Version Windows 8.1 64 bit
Build System VS2015
@dorodnic
Copy link
Contributor

dorodnic commented Oct 3, 2016

Hi tasptz,
It sounds very much like a known bug on Windows 8.1. You can verify by repeating your tests on Windows 10. Alternatively, check the call-stack of the thread stuck on set_option - on Windows 8.1 calls to IKsControl::KsProperty would sometimes dead-lock inside the driver.
You can try installing KB3075872 and KB2919355, designed specifically to solve this problem.
The only potential software work-around we came up with is calling IKsControl::KsProperty on a separate thread and then killing it if it is taking too long. It is complicated and we run the risk of leaking resources, so we decided not to implement this in librealsense.

@dorodnic dorodnic added the SR300 label Oct 3, 2016
@tasptz
Copy link
Author

tasptz commented Oct 4, 2016

Hi dorodnic,
I had the second update already installed - so the first one seems to have solved the problem. Thanks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants