Search Issue Tracker

Fixed in Unity 2018.2



Found in


Issue ID




Can not send network message. Receiver can not keep up with the amount of data sent when deep profiling player




Priority: 4Not yet prioritized for a release


Severity: 3Secondary functionality broken

Steps to reproduce:
1. Open user attached project
2. Build and Run the project with Development Build and Autoconnect Profiler checked (delete the required displayed shader files in the error field if the project does not build)
3. Make sure deep profiling player is properly running
4. Leave the game running for a few minutes
5. Notice "Can not send network message. Receiver can not keep up with the amount of data sent" messages in the player's log.

Expected result: deep profiling data should be properly sent to the editor

Reproduced in: 2018.1.0b1, 2017.3.0f1

Comments (22)

  1. 573f0a24dd0632302213c867b3b1b91a?d=mm


    Dec 08, 2018 13:27

    Just experienced this today. I'm using Unity 2018.2.17.

  2. 5505f9574572edd1103f430cad8631fe?d=mm


    Sep 20, 2018 18:09

    The quick fix, in the latest version(s) of Unity, is to disable "Development Build".

  3. 17c42327ea95a3f9dc114ff5cb4770b0?d=mm


    Sep 07, 2018 06:11

    Yep, Unity 2018.2.6f1 and ArKit 1.5 trying to connect with ARKitRemote.

    Have been getting this since I tried to work with ArKit a few months back and was never able to get ARKitRemote to run.

    Been in all forums and tried everything including the zeroichi fork.

  4. 933eb47463f30e21cbe1090bbc4ca373?d=mm


    Aug 27, 2018 16:26

    Also experiencing this, in 2018.2.3f1. Not using ARKit like some of the other comments are, just regular Unity.

  5. 5505f9574572edd1103f430cad8631fe?d=mm


    Aug 22, 2018 20:17

    Same issue, error message spammed in xcode output.

  6. 2f1884ffd0d06fa7541684bcfa7857c4?d=mm


    Aug 17, 2018 03:16

    Here is temporary "fork" with a patch from blog post that fixes this issue for me:

  7. 4fe7cfb5d55b911fb1ca828dcc7d3f65?d=mm


    Aug 16, 2018 07:04

    still have this issue on Unity 2018.2.2f1.

    I executed a standalone build with 'development build' & 'Autoconnect profiler'.
    and, the application shut down at different timing every time I execute.

    Please fix this one to properly profile the build.

  8. 48381a515479b39da8cc48d5494e02c9?d=mm


    Aug 11, 2018 14:55

    Is NOT fixed in 2018.2 - I'm seeing it on 2018.2.2f1. It also causes my browser to crash for some reason, and usually causes Unity to become completely non-responsive. I'm testing on Android, over USB, and just watching the profiler tick along when the symptom occurs. Can replicate at will.

  9. 2f1884ffd0d06fa7541684bcfa7857c4?d=mm


    Aug 10, 2018 03:53

    I'm still seeing this issue.

  10. 1cd3e654a040b8abb7c686d8eb50feb3?d=mm


    Aug 06, 2018 10:29

    Issue still exists in 2018.2.0f2

All about bugs

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