Search Issue Tracker
Fixed in 2018.1.X
Fixed in 2017.3.X, 2017.4.X
Votes
7
Found in
2017.3.0a5
2017.3.0b7
Issue ID
964953
Regression
Yes
EditorOverhead takes significantly more time after 2017.3.0a5
Steps to reproduce:
1. Open user's attached project
2. Play the scene
3. In profiler, sort methods by "Time ms"
4. Observe EditorOverhead is taking 2-4 ms
Expected result: Overhead is not slower in newest Unity versions, takes 0.04-0.06 ms
Actual result: Overhead is slower than it was older Unity versions, takes 2-4 ms
Reproduced with: 2017.3.0f3, 2017.3.0b7, 2018.1.0a7
Not reproduced with: 5.5.5p1, 5.6.4p1, 2017.1.2p4, 2017.2.1f1, 2017.3.0a4
Regression since 2017.3.0a5
Fixed in 2018.2.0a2
Comments (17)
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
castor76
Feb 17, 2018 16:43
This is still not fixed in 2017.3.p4... When we will be able to see the fix?
esteban16108
Dec 30, 2017 11:45
Sorry, my Unity Version is
Version 2017.3.0f3 (a9f86dcd79df)
Tue, 12 Dec 2017 13:41:20 GMT
Branch: 2017.3/staging
esteban16108
Dec 30, 2017 11:43
In my case it's very significant and you can see the scene dragging.
Look:
http://prntscr.com/hu5l0p
You can see there that is taking the whole thing down... what can be causing this?
Thanks.