You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Even after calling close() or destroy(), the promise created on unix-read.ts:41 never resolves / rejects. As a result, Node.js is prevented from exiting indefinitely.
See sample output from the minimal repro program above.
What should have happened?
The program should be able to exit cleanly after close() / destroy() is called.
Additional information
No response
The text was updated successfully, but these errors were encountered:
Node Version
V18.16.1 (MACOS) V20.15.0(WIN10,WIN11 )
Electron Version
No response
Platform
MACOS12.1 WIN11 WIN10
Architecture
x64
Hardware or chipset of serialport
FT232R USB UART
I use serialport and I use it in node-red MACOS OS,and it runs good. But when It runs on WIN10 or WIN11 , it occurs some problems. ACCESS DENIED. It took me 3days ,and finally I found .When I close the port ,even await ,It still cant close clearly.I have to add some delay to solve the problem.
So can anyone find the solution?
SerialPort Version
12.0.0
Node Version
v18.18.2
Electron Version
No response
Platform
Linux devfox 6.8.2-arch2-1 #1 SMP PREEMPT_DYNAMIC Thu, 28 Mar 2024 17:06:35 +0000 x86_64 GNU/Linux
Architecture
x64
Hardware or chipset of serialport
Prolific Technology, Inc. PL2303 Serial Port / Mobile Phone Data Cable
What steps will reproduce the bug?
SerialPort
instance and attach adata
callback:serialport.on('data', (data) => { ... })
.SerialPort
instance:serialport.close(...)
. (Addingpause()
ordestroy()
produces the same result)Minimal repro: serialport-test.ts
What happens?
Even after calling
close()
ordestroy()
, the promise created on unix-read.ts:41 never resolves / rejects. As a result, Node.js is prevented from exiting indefinitely.See sample output from the minimal repro program above.
What should have happened?
The program should be able to exit cleanly after
close()
/destroy()
is called.Additional information
No response
The text was updated successfully, but these errors were encountered: