Port never seems to close about ardity

[Naphier]

Further info: Sometimes when closing Unity I get a gc error dialogue that locks the editor.

[dwilches]

Hello Naphier,

Which version of the library are you using?
Could you try with version serial-comm-unity-1.0.0 to see if the problem happens with that as well?

If the problem persists, is it possible to see your code?

[Naphier]

My code is at the above gist in the first message. Execution flow to reproduce is connect to device, disconnect (i.e. SerialPortController.Shutdown()), and then reconnect. This is also happening even if I disconnect, stop the editor application, and then start a new connection. It's like the port is just never closing.

With 1.0.0 the problem persists, but now also getting a null exception on AbstractSerialThread.Runforever()'s SendToWire loop as serialPort is null at that point:

Unknown exception: Object reference not set to an instance of an object   at SerialThreadLines.SendToWire (System.Object message, System.IO.Ports.SerialPort serialPort) [0x00008] in E:\@Documents\Consulting Projects\VRR\FlexPointController-repo\FlexPointController\Assets\SerialComm\Scripts\Threads\SerialThreadLines.cs:34 
  at AbstractSerialThread.RunForever () [0x000a3] in E:\@Documents\Consulting Projects\VRR\FlexPointController-repo\FlexPointController\Assets\SerialComm\Scripts\Threads\AbstractSerialThread.cs:170 
UnityEngine.Debug:LogError(Object)
AbstractSerialThread:RunForever() (at Assets/SerialComm/Scripts/Threads/AbstractSerialThread.cs:179)

Thanks!

[Naphier]

Further note on the exception from above:

This happens like so:

• connect,
• disconnect,
• connect,
• IO exception : operation aborted due to thread exit or application request), disconnect.
• disconnect
• Unknown exception: Object reference not an instance...

Still not sure if this is a device issue, driver issue, or .NET issue. I'm trying to get my hands on another device to eliminate at least one of those. Will also check on another PC to see if I can eliminate the possibility of driver issue. But it seems that serialPort.Close() just isn't doing its job 😦

[Naphier]

I've confirmed with the manufacturer that it is indeed the device. I apologize for the bunk issue. Thanks for your hard work!

[dwilches]

Thanks for letting me know! Good luck with your project.

…

On May 24, 2017 8:44 PM, "Sean Mann" ***@***.***> wrote: Closed #8 <#8>. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#8 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ADyo6XGKMDqEIKXwCSweIRIy0n_4_T8gks5r9PkzgaJpZM4Njqyf> .