[7.5.2] OSError: [Errno 10048] error while attempting to bind on address ('127.0.0.1', 8085)

[xoriole]

From reporter - 7.5.2

platform : Windows-10 (AMD64)
uptime : 64.10835766792297

Traceback (most recent call last):
File "src\tribler-gui\tribler_gui\event_request_manager.py", line 138, in <lambda>
File "src\tribler-gui\tribler_gui\event_request_manager.py", line 80, in on_error
tribler_gui.event_request_manager.CoreConnectTimeoutError: Could not connect with the Tribler Core within 60 seconds
[PID:5376] 2020-08-25 15:41:08,656 - ERROR <session:366> Session.unhandled_error_observer(): Unhandled exception occurred! [Errno 10048] error while attempting to bind on address ('127.0.0.1', 8085): une seule utilisation de chaque adresse de socket (protocole/adresse r�seau/port) est habituellement autoris�e
--LONG TEXT--
Traceback (most recent call last):
File "src\run_tribler.py", line 81, in start_tribler
File "src\tribler-core\tribler_core\session.py", line 397, in start
File "src\tribler-core\tribler_core\restapi\rest_manager.py", line 77, in start
File "lib\site-packages\aiohttp\web_runner.py", line 100, in start
File "lib\asyncio\base_events.py", line 1463, in create_server
OSError: [Errno 10048] error while attempting to bind on address ('127.0.0.1', 8085): une seule utilisation de chaque adresse de socket (protocole/adresse r�seau/port) est habituellement autoris�e

--CONTEXT--
{'message': 'Task exception was never retrieved', 'exception': OSError(10048, "error while attempting to bind on address ('127.0.0.1', 8085): une seule utilisation de chaque adresse de socket (protocole/adresse r�seau/port) est habituellement autoris�e"), 'future': <Task finished name='Task-1' coro=<start_tribler_core.<locals>.start_tribler() done, defined at src\run_tribler.py:50> exception=OSError(10048, "error while attempting to bind on address ('127.0.0.1', 8085): une seule utilisation de chaque adresse de socket (protocole/adresse r�seau/port) est habituellement autoris�e")>}

Multiple users reported this issue

[sentry-for-tribler]

Sentry issue: TRIBLER-1R

Still reproduced in 7.5.4.

[sentry-for-tribler]

Sentry issue: SENTRY-FOR-760-E

Still multiple reports in 7.6.0

[devos50]

I'm not sure if there is much we can do about this. It probably means that another process listens on port 8085. We can increment the port until we find a free one, but that requires additional communication between the core and GUI, since they both have to use the same port.

[drew2a]

Still multiple reports in 7.6.1

[sentry-for-tribler]

Sentry issue: SENTRY-FOR-760-16