Search Issue Tracker
Fixed in 2018.3.X
Votes
0
Found in
2018.2.0b9
Issue ID
1052147
Regression
No
Incremental compiler possibly leaks memory when recompiling project a lot
How to reproduce:
1. Open user-submitted project (Link in the edit section)
2. Open "SampleScene.unity" scene
3. In Unity menu select Tools->Compilation->ResetCompilationStressTestFlags
4. In Unity menu select Tools->Compilation->Force recompile UNTIL ASSEMBLY COPYING ERROR SHOWS UP
Expected result: Unity never crashes
Actual result: Unity crashes after approximately an hour of recompilation jobs
Reproducible with: 2018.1.7f1, 2018.2.0b11
Could not test with: 2017.1, 2017.2, 2017.4(Incremental compiler was not introduced yet); 2018.3.0a3(Package Manager is unavailable yet)
fixed in 0.0.42-preview.15
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Non-multisampled texture binding errors are logged when running the DepthBlit URP scene with MSAA enabled on Vulkan
- The Editor does not recognize code errors in generic classes when using C# Source Generator to generate serialization code
- Long Sprite names are not truncated in the Inspector window name label and the preview labels when a Sprite with a long name is selected
- NullReferenceException is logged when undoing Deletion of a Visual Query Block of a Search Expression
- “Unsupported type MinMaxCurve” error and “Could not register property modification for animation binding…” warnings are thrown after moving playhead when Particle System Property is added to Animation window
Add comment