Search Issue Tracker
Won't Fix
Votes
0
Found in
2021.3.8f1
2022.1.12f1
2022.2.0b3
2023.1.0a5
Issue ID
UUM-11168
Regression
No
Unclearable "Diagnostic switches are active" warning duplicates every time a script is reimported
How to reproduce:
1. Open the user’s attached “UrpMatConversion” project
2. In the main menu bar, select “Edit” → “Preferences…”
3. Select “Diagnostics” in the Preferences window
4. Click the “I understand, show me the settings” button if you do not have Diagnostics enabled
5. Expand the “Editor” menu
6. Enable the "ModuleManagerLogging", "PreviewSceneActivity" and "WriteOutCallStackTraces" flags
7. In the Project window, right-click on Assets/MyScript and select “Reimport”
8. Observe the Console
Expected result: Only one unclearable log message is shown: “Diagnostic switches are active and may impact performance or degrade your user experience.”
Actual result: Two identical unclearable log messages are shown
Reproducible with: 2021.3.8f1, 2022.1.12f1, 2022.2.0b3, 2023.1.0a5
Couldn’t test with: 2020.3.37f1 (Diagnostics menu not available)
Reproducible on: Windows 10
Notes:
1. Restarting the Editor resets the log amount to one
2. Some versions may stack up more than 2 unclearable logs (2021.3.8f1, for example)
-
Thanitsak
Nov 15, 2022 10:23
The problem solved, check this forum https://forum.unity.com/threads/diagnostic-switches-are-active-profileopencljobs.1354289/
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
- Character spacing value is not applied when using a specific font asset
- [Android][IL2CPP] Player crashes on __memcpy_aarch64_simd+276 when invoking native code via a plugin on some ARM64 Android devices
- [Android]Resources fail to load when the AAB build contains a large Addressables Bundle
- Unity is loading internal version of SharpZipLib instead of local version
- The Context Menu items are ordered incorrectly
Resolution Note:
After investigation, we have deemed this a low priority issue that won't be fixed in the near future because it is too costly to implement or because there are risks of introducing other problems doing so.
If you feel this is a wrong assessment please reach out again, providing more details about the impact of that issue.