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
{{ message }}
Repository navigation
SerialPort.setBreak() consistently takes ~510ms to finish #588
Starting with v2.10.3, the port.setBreak() call always takes between 509 and 512 milliseconds to complete, compared to less than one millisecond in the versions before. (Measured using measureTimeMillis from Kotlin's standard library.)
While the DMX protocol generally does not require very precise timing, ~500ms is definitely too long.
What OS is this on? Are you certain that it's the setBreak() function that is being delayed? I'm asking because there are literally no code changes to the setBreak functionality between v2.10.2 and v2.10.3 (or even between v2.10.2 and the current version).
It will probably be some time before I return to the project where I encountered this problem, if ever. It seems like I was the only person with the problem, so feel free to close this issue.
Now, to answer the first part of your question: It was on Void Linux.
Activity
hedgecrw commentedon Oct 31, 2025
What OS is this on? Are you certain that it's the
setBreak()function that is being delayed? I'm asking because there are literally no code changes to the setBreak functionality between v2.10.2 and v2.10.3 (or even between v2.10.2 and the current version).moritzruth commentedon Jan 17, 2026
Hey, I apologize for not responding sooner.
It will probably be some time before I return to the project where I encountered this problem, if ever. It seems like I was the only person with the problem, so feel free to close this issue.
Now, to answer the first part of your question: It was on Void Linux.