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

Networking

-

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.

  1. 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.

Log in to vote on this issue

Comments (1)

  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

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.

Latest issues

See all new issues