Fix: Isolate can't be killed on "onPause", and increases infinitely. #82
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
As stated in #46, SerialPortReader fails to kill Isolate on the "onPause"` event and creates a new one on the "onResume" event.
So, Isolates increase infinitely.
Below is the example code to reproduce the problem.
You'll see the increased Isolates in the call stack pane, as in the picture.
I'm not sure, but the onPause and onResume events are unnecessary,
because the serial port can buffer input data.
Or, if SerialPortReader needs to handle resume/pause events,
_isolate?.kill(priority: Isolate.immediate);
also works well.