-
-
Notifications
You must be signed in to change notification settings - Fork 1k
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
Access violation after 2 or 3 successive writes #1006
Comments
Version 4.0.6 is Released please give it a try and let me know if it fixes this. |
No, |
I've found out that if move callback.Call in EIO_AfterWrite to the place where it was in serialport@3.1.2, then program stops crashing. Patch:
|
I've been testing this patch under Windows and Linux (Banana Pi) all this day. |
I think problem is caused by patch #808.
|
Can you try 5.0.0-beta5? |
Other reports have confirmed this is fixed. |
SerialPort version: 4.0.5
NodeJS Version: 4.5.1
Operating System and Hardware Platform: Windows XP /7/8/10
Summary of Problem:
After migration to serialport@>=4 my program started:
Crash condition:
2 or 3 successive writes
Test:
Output:
As you can see for-loop does not complete.
On serialport@3 it did.
NtTrace:
Complete log
Work-around:
add one of these lines after write
yield cb => sp.drain(cb)
yield cb => setImmediate(cb, 0)
The text was updated successfully, but these errors were encountered: