Search Issue Tracker
Fixed in 2021.3.28f1
Fixed in 2021.3.X, 2022.3.X, 2023.1.X, 2023.2.X, 2023.2.0a16
Votes
0
Found in
2020.3.47f1
2021.3.22f1
2022.2.14f1
2023.1.0b11
2023.2.0a9
Issue ID
UUM-32851
Regression
No
[IL2CPP] Process.ProcessName includes the full path when reporting the name
Reproduction steps:
1. Open project “IL2CPP Backend Issue“
2. Enable “Build Settings\Development Build”
3. Build the project with IL2CPP scripting backend
4. Observe the development build console
Expected result: “Containing process is named: IL2CPP Backend Issue” error message is thrown
Actual result: “Containing process is named: \Device\HarddiskVolume2\…\IN-36897_IL2CPP Backend Issue\Builds\IL2CPP Backend Issue” error message is thrown
Reproducible with: 2020.3.47f1, 2021.3.22f1, 2022.2.14f1, 2023.1.0b11, 2023.2.0a9
Reproducible on: Windows 11
Notes:
- Based on Microsoft documentation (https://learn.microsoft.com/en-us/dotnet/api/system.diagnostics.process.processname?view=netstandard-2.0) the full path should not be included
- Building the project with Mono scripting backend correctly removes the path from the process name
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Active quality level set on a new Universal 2D project is not the default quality level when creating a new project
- Inspector Open button does nothing when navigating to a different folder with a locked asset
- Pre-generated XML serializers fail to deserialize types that use polymorphism when the Player is built with the IL2CPP scripting backend
- Editor crashes with error "Failed to present D3D11 swapchain due to device reset/removed" and Player freezes when rendering a particle system while using modified URP package on DX11
- Crash on Scripting::LogException when async HTTP callback executes after scripting domain teardown
Add comment