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
Hi, guys,
I've encountered an issue where minitouch does not terminate properly when I send a SIGINT signal (using Ctrl+C) in the Win-PS terminal. After terminating minitouch with Ctrl+C, attempting to run it again results in a "binding socket: Address already in use" error. This suggests that the previous instance of minitouch did not release the port it was using.
Steps to Reproduce:
Start minitouch on an Android emulator/device using the command: adb shell /data/local/tmp/minitouch.
Terminate minitouch using Ctrl+C.
Attempt to run minitouch again using the same command.
Expected Behavior:
Minitouch should terminate gracefully upon receiving a SIGINT signal and release any resources it was using, including the port.
Actual Behavior:
Minitouch does not seem to release the port it was bound to, leading to a "binding socket: Address already in use" error upon attempting to run it again.
Environment:
Operating System: Windows 10
Android device/emulator model: emulator-5554
Android version: Android 7.1.2
Additional Information:
Running adb -s emulator-5554 shell ps | findstr minitouch confirms that the minitouch process is still running after attempting to terminate it with Ctrl+C.
Temporary workaround: Manually killing the process using adb shell kill [PID] allows minitouch to be run again.
I believe this might be a bug with how minitouch handles the SIGINT signal. Any assistance or insights into this issue would be greatly appreciated.
The text was updated successfully, but these errors were encountered:
Hi, guys,
I've encountered an issue where minitouch does not terminate properly when I send a SIGINT signal (using Ctrl+C) in the Win-PS terminal. After terminating minitouch with Ctrl+C, attempting to run it again results in a "binding socket: Address already in use" error. This suggests that the previous instance of minitouch did not release the port it was using.
Steps to Reproduce:
adb shell /data/local/tmp/minitouch
.Expected Behavior:
Minitouch should terminate gracefully upon receiving a SIGINT signal and release any resources it was using, including the port.
Actual Behavior:
Minitouch does not seem to release the port it was bound to, leading to a "binding socket: Address already in use" error upon attempting to run it again.
Environment:
Additional Information:
adb -s emulator-5554 shell ps | findstr minitouch
confirms that the minitouch process is still running after attempting to terminate it with Ctrl+C.adb shell kill [PID]
allows minitouch to be run again.I believe this might be a bug with how minitouch handles the SIGINT signal. Any assistance or insights into this issue would be greatly appreciated.
The text was updated successfully, but these errors were encountered: