Search Issue Tracker
Won't Fix
Votes
2
Found in
5.4.0b14
Issue ID
795811
Regression
No
GUI in NetworkManager and NetworkLobbyPlayer leads to unnecessary GC Allocation
Having a NetworkManager or NetworkLobbyManager in a scene allocates 464B per call even though Network GUI is not being drawn and scripts are empty.
1. Open the attached project 'GC'
2. Open the available scene
3. Play scene
4. Open the Profiler window
5. In 'CPU Usage' notice that GUI.Repaint collects 464B per call
Expected: When NetworkManager script is completely empty, GC should not be allocated on GUI
User suggests removing the OnGUI() code from NetworkManager and NetworkLobbyPlayer classes and placing them into it's own Network GUI Display component.
Comments (1)
-
ProfTroy
Jul 30, 2016 20:23
This is actually causing me the difference of hitting performance milestones and not hitting those performance milestones.
Having a NetworkLobbyManager and a NetworkDiscovery item in the scene causes serious GUI.Repaint issues with GC hits.
Can this get bumped to have the OnGUI removed from the network packages?
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
- Editor crash on "PPtr<Shader>::operator Shader*() const" when checking in changes with a very long comment in Unity Version Control window
- [Ubuntu] Toolbar and menu items for Version Control lack spaces in text on Linux
- Unity Version Control window Pending Changes tab’s Item checkbox is unresponsive when clicked and the item list is empty
- Audio stuttering occurs when heavy processing is performed while OnAudioFilterRead is in use
- Inconsistent Node search results in VFX Graph
Resolution Note:
Mass closure of UNET Bugs.
As UNET is Deprecated we are moving to low maintenance mode, where critical issues can get fixes.
Closing this bug as part of cleaning-up the Bug List.
If you feel this bug is really a road-blocker, you can reopen the bug and we will work this one.