Search Issue Tracker
Fixed in 2020.1.X
Votes
0
Found in
2020.1.0a12
Issue ID
1197768
Regression
Yes
[UMPE] logging appears when launching or building Unity 2020.1.0a12 via the console
Steps to reproduce
- Install Unity 2020.1.0a12
- Launch Unity from the command line using
./2020.1.0a12/Editor/Unity -batchmode -quit
- Notice issue >> [UMPE] Parent Process Locking Mutex Name: /umpe5_1909f56bfc062723c751e8b465ee728b
Expected:
If this information is important to the user it should be logged in the editor log. Only appears in the console and not the editor log.
Tested
Unity 2020.1.a12
Ubuntu
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Error “Shader error in 'YSCloudCover': call to 'tex3D' is ambiguous at Assets/YSCloudCoverText.shader(606) (on d3d11)“ is present when compiling tex3D shader with DXC
- Placeholder asset is not loaded with Advertisement Legacy sample when using the latest version of the package
- Addressables content build fails but the Player build is successful when building a development build
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
Add comment