Port related issue (IDFGH-14333)

[Manasabalakrishna]

Answers checklist.

• I have read the documentation ESP-IDF Programming Guide and the issue is not addressed there.
• I have updated my IDF branch (master or release) to the latest version and checked that the issue is present there.
• I have searched the issue tracker for a similar issue and not found a similar issue.

General issue report

port is used by otjer task
ninja failed with exit code 1, output of the command is in the C:\Users\ManasaJB\hello_world\build\log\idf_py_stderr_output_22332 and C:\Users\Manasa

1.if i stop the terminal and again rerun the code its showing termianl closed
2.if i run the code 2 times again out put showing port is not availbke
3.each time i got stuck like this even if i remove port and close ide it doesnot works i need to compleetely turn off my pc then it willl work and again after 2 times it will gte stuck

steps took to resolve downgarde trhe version and confirm that port is not being used in any other task .

[KonstantinKondrashov]

Hi @Manasabalakrishna!
It seems the COM port is not being released properly when you close the terminal. Always properly close the terminal or stop the idf monitor before closing the terminal or IDE.

• Before closing the terminal, ensure you stop the connection (e.g., Ctrl+] in idf.py monitor).
• If stuck, open Task Manager (Ctrl+Shift+Esc), find any process using the port (e.g., Python or terminal emulator), and end it.
• If the port still doesn’t work, unplug and replug the device.

If does not help please provide more information on what IDE you use, what esp-idf version, OS, etc.

[Manasabalakrishna]

Thanks @KonstantinKondrashov
**Each time when port got stuck **
open Task Manager > Details> see for Python.exe
end the python .exe task ,and this is working fine for me.

[peterdragun]

Hi @Manasabalakrishna, can you please confirm that this does not happen if you close the IDF Monitor properly before closing the terminal (with CTRL+]), as Konstantin suggested in the previous reply?

[Manasabalakrishna]

Hello, The issue was there even if when I give ctrl+] .Only when I end python.exe it works.

…

On Tue, 7 Jan 2025 at 14:53, Peter Dragun ***@***.***> wrote: Hi @Manasabalakrishna <https://github.com/Manasabalakrishna>, can you please confirm that this does not happen if you close the IDF Monitor properly before closing the terminal (with CTRL+]), as Konstantin suggested in the previous reply? — Reply to this email directly, view it on GitHub <#15123 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BJ65KEQEKHJEKKAUVMBHGML2JOMITAVCNFSM6AAAAABUPPV2T6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNZUG44DIOJSGM> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[peterdragun]

I am sorry but I was not able to reproduce the issue. Can you please provide some more information? Based on the screenshot I assume you are using Windows 11. How are you executing IDF Monitor and esptool? are you using some IDE (integrated terminal or buttons in IDE)? If you are using IDE, can you reproduce the same issue if you don't use the IDE but rather Powershell or the command line directly? Thank you

My setup: Win11, both command line and PowerShell work even if I don't close the Monitor before closing the terminal. The only way I can reproduce this is when I keep the monitor running in one window and try to connect to the same chip from another window, which is expected behavior.

[dobairoland]

I'm closing this for inactivity. We can reopen it if there is more information to work with.