Process.WaitForExit() deadlock when running multiple processes on linux with .net7 #80563

Activity

1. ghost added

   area-System.Diagnostics.Process

   on Jan 12, 2023
2. ghost added

   untriagedNew issue has not been triaged by the area ownerNew issue has not been triaged by the area owner

   on Jan 12, 2023
4. adamsitnik commented on Jan 13, 2023

   

   adamsitnik

   on Jan 13, 2023

   Member

   More actions

   @tmds is there any chance you could take a look?
5. tmds commented on Jan 14, 2023

   

   tmds

   on Jan 14, 2023

   Last edited by tmds

   Member

   More actions

   @kirnosenko you've only observed this issue in a container, right?

   You can work around it by changing the entrypoint to something like:

   ENTRYPOINT ["/bin/sh", "-c", "dotnet <your_assembly>.dll"]
   

   #79817 fixes this and is backported for an upcoming 7.0 patch release.
6. kirnosenko commented on Jan 14, 2023

   

   kirnosenko

   on Jan 14, 2023

   Author

   More actions

   @tmds yes I run it in container, unfortunately your suggestion makes no any difference, still has a deadlock.
7. tmds commented on Jan 17, 2023

   

   tmds

   on Jan 17, 2023

   Member

   More actions

   unfortunately your suggestion makes no any difference, still has a deadlock.

   Ah, I thought it would be enough to make the .NET process have another pid than 1, but that's not true.

   If you add the --init flag to the docker run command (which adds an init process as pid 1), the deadlock disappears.

   #79817 fixes this issue.

   👍React with 👍2Reacted by Semyon Kirnosenko and Adam Sitnik
8. adamsitnik commented on Jan 18, 2023

   

   adamsitnik

   on Jan 18, 2023

   Member

   More actions

   @tmds thank you for your help!
9. adamsitnik

   closed this as not plannedon Jan 18, 2023
10. ghost removed

    untriagedNew issue has not been triaged by the area ownerNew issue has not been triaged by the area owner

    on Jan 18, 2023
11. ghost locked as resolved and limited conversation to collaborators on Feb 17, 2023