Search Issue Tracker
Won't Fix
Votes
0
Found in
2017.2.0f3
Issue ID
976109
Regression
Yes
[Collab] Null Reference Exception errors are thrown when using Collaborate and closing/dragging Project tab
1. Create a new Unity project and open it
2. Right click on Project tab and add another Project tab (Add Tab --> Project)
3. Close the added Project tab and notice that no errors are thrown in the console
4. Turn on Collaborate, notice that a few Null Reference Exceptions are thrown in the console
5. Repeat steps 2 and 3
Expected result: No errors are thrown in the console
Actual result: Null Reference Exceptions are thrown in the console when closing/dragging/opening Project tab
Regression introduced with - 2017.1.0p3
Reproducible with - 2018.1.0a7, 2017.3.0f2, 2017.2.1f1, 2017.1.2p3, 2017.1.0p3
Not reproducible with - 2017.1.0p2
Notes:
1. Happens with other tabs as well, but the repro with the Project tab is the most consistent one
2. Seems that turning off Collab does not solve the issue and the errors keep re-appearing, but the errors do not happen before turning on Collab service
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Crash on ExtractActiveCasterInfo when navigating the scene view in a project with specific lighting data
- Build Profile name increments when numeric suffix is removed from duplicate Profile name
- "Unrecognized block header in profiler data file, stopping deserialization" error is shown and no more profiler data is recorded when the Player is connected and profiler recording is enabled/disabled few times
- Shader error and warnings thrown when setting HDRP as an Active Target in Blank Shader Graph
- Visual Studio Code does not integrate with the project when the .slnx project is opened
Add comment