Search Issue Tracker
Won't Fix
Votes
1
Found in
2020.1.0a15
Issue ID
1202771
Regression
Yes
[Perforce] Unity Editor drastically slows down if a currently connected MFA enabled user logs off
How to reproduce:
1. Create a new project in your preferred workspace and open it
2. Connect to your MFA enabled server via P4V and then do the same in Unity
3. Logoff through P4V (Connection -> Log off)
4. Go back to the Unity Editor and observe the poor performance
Expected result: The editor does not stutter/vcs disconnects with a warning or error
Actual result: The editor drastically slows down and vcs is still shown as "connected"
Reproduced in: 2020.1.0a16, 2019.3.0f2, 2019.2.15f1, 2018.4.14f1
Not reproducible in: 2017.4.35f1 (The editor immediately disconnects vcs without any major slow downs)
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
- PlayerPrefs get corrupted when a minimized fullscreen Player is closed through the Taskbar
- "To Debug, run app with -diag-job-temp-memory-leak-validation cmd line argument. This will output the callstacks of the leaked allocations." warning is printed when JobTempMemoryLeakValidation switch is enabled
- Main Thread stalling when loading Audio Source asset asynchronously while preloading another Audio Source asset
- Material artifacts occur in the Material Preview window when baked lighting is applied to scenes
- “ArgumentOutOfRangeException” after saving, reseting and re-add Default Tile Palette Tools to the list in Preferences window
Resolution Note (2021.2.X):
Affects limited number of users and has an easy workaround (don't log out of MFA in P4V). Possibility that this is actually a P4 issue underlying this also.