search

jkuusama / LitePlacer-retired-experiment

3 stars 15 forks source link

Camera management is not robust #11

Open mrandt opened 9 years ago

mrandt commented 9 years ago

To reproduce problem:

  1. Connect two USB cameras
  2. Start application and configure up and down cam
  3. Close application
  4. Unplug one or both USB cameras
  5. Start application again
  6. Application crashes with "unrecoverable error"
thethereza commented 9 years ago

try to generate a stack trace of the crash dump. how many other cameras do you have connected?

mrandt commented 9 years ago

Will try that. I have exactly two cameras connected - one is Logitech C270 (up cam) and the other is a Ednet 1080p (down cam) - no other imaging hardware.

MaWa53 commented 9 years ago

Just started a test run of V2 after V1 works as far as I have come with my setup.

Using standard cameras I get to see only the up camera when I start the V2. The combos are correctly seleted. When I press (Re)Start Cameras program crashes due to null values for isProcessingThreadAvailable and isNewFrameAvailable in MyAsyncSource.Free.

thethereza commented 9 years ago

If the cameras are the same in the combox then it will only open one camera. If the two are set correctly it should open both and if one doesn't open, which is something that I've experienced, then try quitting the application restarting it three more times usually to see if that fixes the problem. Let me know what happens. If that fixes it or works, but I'm not sure what the problem is, I think it has to do something with the way the drivers work. If you close the application properly, then it continues to work OK. It only seems to be a problem when starting the program after a crash

On Jul 13, 2015, at 9:00 AM, MaWa53 notifications@github.com wrote:

Just started a test run of V2 after V1 works as far as I have come with my setup.

Using standard cameras I get to see only the up camera when I start the V2. The combos are correctly seleted. When I press (Re)Start Cameras program crashes due to null values for isProcessingThreadAvailable and isNewFrameAvailable in MyAsyncSource.Free.

— Reply to this email directly or view it on GitHub.

thethereza commented 9 years ago

actually i just tried clicking reopen cameras and it fixed the problem i was having. please try to provide me with some more debugging information

mrandt commented 9 years ago

In SVN Release 18 I could no longer reproduce the problems. Clicking "Restart Cameras" fixes the display problem for me after changing camera configuration.

@MaWa53 does it work for you as well? Let us know if there are additional issues, otherwise I will close this issue.