Search Issue Tracker
Won't Fix
Votes
0
Found in
2019.1.0a13
2019.4
2020.1
2020.2
2021.1
Issue ID
1288973
Regression
Yes
"Editor.log" is filled with Non-readable symbols when Running multiple Instances of editor
Steps to reproduce:
1. Open two Instances of Unity editor
2. Open the "Editor log" with an advanced text editor (visual studio code) from the default editor log location "C:\Users\user\AppData\Local\Unity\Editor"
3. Delete everything from the "Editor.log" and save it
4. Focus back on the editor windows and switch between them
5. Open the "Editor.log" again
Expected results: Normal logs are displayed
Actual results: Non-readable symbols are displayed in the first line or throughout the whole file
Reproducible with: 2019.1.0a13, 2019.4.15f1, 202.1.15f1, 2020.2.0b13, 2021.1.0a7
Not Reproducible with: 2018.4.29f1, 2019.1.0a12
Note: macOS does not update "Editor.log" after deleting its content while running the editor
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Objects with Universal Render Pipeline/Particles/Lit shader are always lit up when changing their Rendering Layer Mask
- PolySpatial “Trying to set shader on a Material Variant.” error is printed in the console when entering Play Mode
- 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
Resolution Note (2021.1.X):
This has been added to the backlog as a feature/improvement.