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

SerialPort.list() crashes Node on Windows while connecting and disconnecting devices. #2339

Closed
gabrieleimotion opened this issue Nov 2, 2021 · 7 comments

Comments

@gabrieleimotion
Copy link

gabrieleimotion commented Nov 2, 2021

💥 BUG

I've experienced the issue where I have a QRCode reader attached to the usb port of my machine, this device goes to stand-by after some time and it gets back when used.
If I query for the device lists in this exact moment the nodejs process crashes without any unhandled exception on promise.

How can I debug this?

serialport version: ^9.2.4
node version: v8.17.0
npm version: v6.13.4

@GazHank
Copy link
Contributor

GazHank commented Nov 2, 2021

Hi @gabrieleimotion are you able to confirm the node and SP versions you are using?

There was a recent change to the windows list function which improved stability, so if you are not already using the latest version then it might be worth a try

@GazHank GazHank added the windows label Nov 2, 2021
@gabrieleimotion
Copy link
Author

@GazHank fair question, I updated my issue adding the version info :)

@GazHank
Copy link
Contributor

GazHank commented Nov 2, 2021

Are you able to upgrade to v12+ of node since the prior versions are no longer supported

@gabrieleimotion
Copy link
Author

gabrieleimotion commented Nov 5, 2021

I tried with v12.22.6 and still crashing without any error on serialport list.
I have a windows machine with 2 serial to tty adapters, 1 barcode reader and 1 brother label printer.
When unplugging the printer the serialport list doesn't crash anymore.

@GazHank
Copy link
Contributor

GazHank commented Nov 6, 2021

If you are still facing issues with a brother printer on the latest version then perhaps #2259 isn't fully resolved yet :-(

@gabrieleimotion
Copy link
Author

Yes that's what I thought, but this happens sporadically and only on a combination of factors.
Is there useful a way I can get more info about the crash?

@stale
Copy link

stale bot commented Apr 16, 2022

This issue has been automatically marked as stale because it has not had recent activity. It will be closed in a week no further activity occurs. Feel free continue the discussion or ask for a never-stale label to keep it open. If this is a support issue, consider sharing it on stack overflow to get more eyes on your problem.

@stale stale bot added the stale-issue label Apr 16, 2022
@stale stale bot closed this as completed Apr 28, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

No branches or pull requests

2 participants