TCPServer keeps its port bound after stopping an app run from Studio
- Status
- Fixed
- Fixed in
- v26.10.1
- Area
- compiler ide
- Source discussion
- https://forum.objo.dev/d/1263-ports
- Last updated
- 2026-10-05
Upvotes
0 upvotes
Uses your Objo forum account.
Public summary
A console app that uses TCPServer with a fixed port works the first time it is run from Studio, but after stopping the app and running it again the server cannot use that port: the previous run's listener is still bound, so the new run fails to listen (typically an "address already in use" socket error) or the server is unreachable. Ports chosen randomly (Port = 0) keep working because each run gets a different port.
The port stays bound until Objo Studio is quit and relaunched, after which the app works again — exactly once.
Expected behaviour: stopping an app run releases everything the app held, including TCP ports, so the next run can bind the same port.