Alpha 8 Keeps crashing

Issue #8 resolved
Christian Dahmen created an issue

Every time I start the PSMoveFreepieBridge it runs for about 1 to 2 minutes, then it crashes without a log or anything.

The only thing I have is a bit from the PSMoveService's log:

[2016-12-31 14:52:44.118]: ServerDeviceView::poll - Device id 0 closing due to no data (100 failed poll attempts)
[2016-12-31 14:52:44.119]: PSMoveController::close - Closing PSMoveController(\\?\hid#{00001124-0000-1000-8000-00805f9b34fb}_vid&0002054c_pid&03d5&col01#8&625b538&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030})
[2016-12-31 14:52:44.135]: ClientConnection::handle_tcp_read_request_header - Failed to read header on connection 6: End of file
[2016-12-31 14:52:44.137]: ClientConnection::stop - Stopping client connection id 6
[2016-12-31 14:52:45.74]: PSMoveController::open - Opening PSMoveController(\\?\hid#{00001124-0000-1000-8000-00805f9b34fb}_vid&0002054c_pid&03d5&col01#8&625b538&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030})
[2016-12-31 14:52:45.76]: PSMoveController::open -   with serial_number: 000704991240
Config file name: "C:\Users\c_dah\AppData\Roaming\PSMoveService\00_07_04_99_12_40.json"
Config file name: "C:\Users\c_dah\AppData\Roaming\PSMoveService\00_07_04_99_12_40.json"
[2016-12-31 14:52:45.253]: DeviceTypeManager::update_connected_devices - Device device_id 0 (PSMove) opened
[2016-12-31 14:53:03.520]: ClientConnection::start - Starting client connection id 7
[2016-12-31 14:53:03.521]: ClientConnection::send_connection_info - Sending connection id to client 7
[2016-12-31 14:53:03.554]: ServerRequestHandler - Start controller(0) stream (pos=1,phys=0,raw_sens=1,cal_sens=0,trkr=0,roi=0)
[2016-12-31 14:53:41.339]: ServerDeviceView::poll - Device id 0 closing due to no data (100 failed poll attempts)
[2016-12-31 14:53:41.340]: PSMoveController::close - Closing PSMoveController(\\?\hid#{00001124-0000-1000-8000-00805f9b34fb}_vid&0002054c_pid&03d5&col01#8&625b538&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030})
[2016-12-31 14:53:41.356]: ClientConnection::handle_tcp_read_request_header - Failed to read header on connection 7: End of file
[2016-12-31 14:53:41.357]: ClientConnection::stop - Stopping client connection id 7
[2016-12-31 14:53:41.611]: PSMoveController::open - Opening PSMoveController(\\?\hid#{00001124-0000-1000-8000-00805f9b34fb}_vid&0002054c_pid&03d5&col01#8&625b538&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030})
[2016-12-31 14:53:41.613]: PSMoveController::open -   with serial_number: 000704991240
Config file name: "C:\Users\c_dah\AppData\Roaming\PSMoveService\00_07_04_99_12_40.json"
Config file name: "C:\Users\c_dah\AppData\Roaming\PSMoveService\00_07_04_99_12_40.json"
[2016-12-31 14:53:42.393]: DeviceTypeManager::update_connected_devices - Device device_id 0 (PSMove) opened

Comments (6)

  1. Elliot Hawkins repo owner

    Sorry to hear about that. Could you answer a few questions? These will help me greatly in figuring out where the problem is.

    Do older versions of PSMoveFreepieBridge, particularly 6 and 7, work fine?

    What version of PSMoveService are you using?

    How many controllers do you have connected in PSMoveService, and how many are tracked in PSMoveFreepieBridge? What are the IDs of the controllers being tracked?

    Does this issue occur when you track different controllers with PSMoveFreepieBridge?

    If you're tracking more than one controller in PSMoveService, have you tried with fewer controllers? Put another way, is there one controller specifically that triggers this issue, and if it's not connected at all everything works fine?

  2. Elliot Hawkins repo owner

    There's a discussion on the PSMoveService Google Groups page where a few others have had this issue, and Hipstersloth suspects it might be related to USB bandwidth. His post shows how you can check if this is the case for you.

    As far as PSMoveFreepieBridge closing, that was caused by how I was handling the opaque service event in the PSMoveService client API. I've uploaded Alpha 9, which changes this behavior. Now it shouldn't close, though if your controller is dropped and not reconnected by PSMoveService, tracking still wont work. The window will also stay open if not closed by the user, so the output can be used for troubleshooting purposes.

  3. Christian Dahmen reporter

    EDIT: Error closed, the new Update fixed any issue i used to see, the Programm doesn't crash anymore.

  4. Log in to comment