Search Issue Tracker
Fixed
Fixed in 2021.3.28f1, 2022.3.5f1, 2023.1.5f1, 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|https://learn.microsoft.com/en-us/dotnet/api/system.diagnostics.process.processname?view=netstandard-2.0|smart-link]) 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
- Animator Controller throws MissingReferenceException after undoing Layer Creation
- Full stack trace is always printed when an exception occurs in an IL2CPP build
- Licensing Client fails to launch when opening Unity Hub (licensing client path is not found)
- Licensing Client fails to launch when opening Unity Hub
- Different custom Shader behavior when GPU Resident Drawer is enabled
Add comment