Search Issue Tracker
Fixed in 2018.2.X
Votes
0
Found in
2017.3.0b7
Issue ID
964264
Regression
Yes
2017.3 Regression in mesh memory size usage
1. What happened
Profiler reports mesh memory size at around 8-9 MBs for the given scene, while other versions (17.1, 17.2, 18.1) have it at ~300 KBs.
Compared to: 2018.1.0a2, 2017.2.0p1, 2017.1.2p2
2. How we can reproduce it using the example you attached
- Scene 'Scene'
- Play
- See Profiler > Memory > Meshes
>>> It is expected to be similar to other versions ~ 250-400 KBs. Actual: ~8.5 MBs
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Editor crashes when debugging a for loop
- Crash on UnityPlayer!profiling::ProfilerManager::DisposeProfilerRecorder+0xa when Player gets relaunched and exited after running for a long amount of time
- [Input system] When releasing one touch and pressing a second touch during a single frame, the second touch is not translated into UI event line OnPointerDown by the InputSystemUIInputModule
- URP Samples - multiple "Attempting to resolve render surface" and other errors appear when setting Quality pipeline asset
- OnDemandRendering.willCurrentFrameRender returns incorrect values in the Player when UnityEngine.Rendering.OnDemandRendering.renderFrameInterval is greater than 1
Add comment