cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Importing Mesh Toolkit into the project leaves .NET Host process running in the background

lukaszdudziak
Copper Contributor

‎May 29 2024 07:44 AM

‎May 29 2024 07:44 AM

Importing Mesh Toolkit into the project leaves .NET Host process running in the background

After importing the Mesh Toolkit into the Unity project, a .NET Host process runs in the background and consumes some resources (around 5-8% of the CPU). 

lukaszdudziak_1-1716993512024.png

 

It points to the dotnet runtime stored in Unity.

"C:\Program Files\Unity\Hub\Editor\2022.3.15f1\Editor\Data\NetCoreRuntime\dotnet.exe"

Closing all Unity instances doesn't close this process. The more projects you open, the more processes run in the background. 

Running an update of Mesh Toolkit in Package Manager will create another .NET Host process in the background. So, it is clearly related to the Mesh Toolkit installer. 

lukaszdudziak_2-1716993625588.png

 

The .Net Host process can be manually killed in the Task Manager and will not reopen itself when the Unity project opens. So, killing it is necessary after each import or upgrade. 

 

The easiest way to reproduce is to create an empty URP project in Unity and import Mesh Toolkit as it is described in the documentation https://learn.microsoft.com/en-us/mesh/develop/build-your-basic-environment/add-the-mesh-toolkit-pac... 

Import Mesh Toolkit. Close Unity when imported and check in Task Manager that .NET Host will be visible on the list. 

Mesh Toolkit versions where it can be reproduced: 5.2406.193, 5.2405.238, 5.2403.243

224 Views
0 Likes
1 Reply
Reply
1 Reply
gleblebedev

‎Jun 05 2024 03:44 AM

‎Jun 05 2024 03:44 AM

Re: Importing Mesh Toolkit into the project leaves .NET Host process running in the background

Dear Łukasz Dudziak,

Thank you for reaching out and bringing this issue to our attention. We are aware of the problem you've encountered and appreciate your patience as we worked to identify the cause.

We have determined that the issue was caused by a bug in Unity, which has been addressed in the Unity version 2022.3.16f1. However, we recommend continuing to use Unity version 2022.3.15f1 for the time being.

We understand the inconvenience this may cause, and we are actively working on a workaround that will be included in the upcoming release of the Mesh Toolkit. This will allow you to continue your work without the need to upgrade Unity beyond the recommended version.

For more details on the bug, you can visit the Unity issue tracker: https://issuetracker.unity3d.com/issues/dot-net-host-process-remains-indefinitely-when-reimporting-a...

If you have any further questions or concerns, please do not hesitate to contact us.
1 Like
Reply