Search Issue Tracker
Fixed in 2017.1.X
Votes
0
Found in
2017.1.0a6
Issue ID
896503
Regression
Yes
[Compilation-Pipeline] If project has "UNetWeaver error" then NullReferenceException appears in Console
Regression - doesn't happen in 5.6.0f3
How we can reproduce it using the example you attached
1 Open attached project
Actual result:
3 "UNetWeaver error"-s appear in Console (expected), and there is 4-th error - NullReferenceException:
"NullReferenceException: Object reference not set to an instance of an object
UnityEditor.Scripting.ScriptCompilation.EditorCompilation.TickCompilationPipeline () (at C:/buildslave/unity/build/Editor/Mono/Scripting/ScriptCompilation/EditorCompilation.cs:550)
UnityEditor.Scripting.ScriptCompilation.EditorCompilationInterface.TickCompilationPipeline () (at C:/buildslave/unity/build/Editor/Mono/Scripting/ScriptCompilation/EditorCompilationInterface.cs:135)"
Expected result:
there should not be NullReferenceExceptions
Comments (1)
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
- [Android] Stage information is not logged when Log Shader Compilation is enabled
- [Vulkan] The memory allocation increases rapidly when there are multiple (three or more) Real-Time Reflection Probes in the Scene
- [macOS] Library folder of the opened project can be deleted which leads to the crash
- “Default Scene” dropdown field contains a spelling mistake “Default Builtin”
- Editor crashes on PPtr<Mesh> after adding Text Mesh and Cloth Components to the same GameObject
hippogames
Oct 22, 2017 14:55
The same problem appeared with no reason. Updating to 2017.2, deleting Library and Restarting OS didn't help.