Closed mrandt closed 8 years ago
I believe when no device is connected, communication should time out and TinyG should automatically go to "disconnected" state on UI.
Of course, that is how it should behave – and does, on my Win8 machine. I’ll investigate.
Best regards,
Juha
From: mrandt [mailto:notifications@github.com] Sent: Thursday, March 5, 2015 2:42 PM To: jkuusama/LitePlacer Subject: [LitePlacer] Application freezes when no USB-TTL converter / TinyG is connected (#2)
When starting the application without hardware controller connected, it freezes completely on my machine (Win7 x64), bloats up memory usage and has to be killed via Task Manager.
From first investigation, issue seems to be located in LitePlacer.SerialComm.Write or further up the call hierarchy...
I believe when no device is connected, communication should time out and TinyG should automatically go to "disconnected" state on UI.
— Reply to this email directly or https://github.com/jkuusama/LitePlacer/issues/2 view it on GitHub. https://github.com/notifications/beacon/AEeI5hmZnEysUeyCmfDG8I7FH6cE6mRRks5nyEaIgaJpZM4Dp_OY.gif
This seems fixed with latest versions. If no TinyG connected, application gracefully goes to "disconnected" state. Suggest close.
When starting the application without hardware controller connected, it freezes completely on my machine (Win7 x64), bloats up memory usage and has to be killed via Task Manager.
From first investigation, issue seems to be located in
LitePlacer.SerialComm.Write
or further up the call hierarchy...I believe when no device is connected, communication should time out and TinyG should automatically go to "disconnected" state on UI.