Search Issue Tracker
Fixed
Votes
0
Found in
2019.1.0a6
Issue ID
1094421
Regression
No
Receiver can not keep up with the amount of data sent error when writing out test results for graphics playmode tests
When trying to get reference images for more than about 10 screenshots when using the grahics playmode test framework (included in the Scriptable Render Pipeline project https://github.com/Unity-Technologies/ScriptableRenderPipeline) an error prevents all the screenshots being written into the test results.
Can not send network message. Receiver can not keep up with the amount of data sent
UnityEngine.PlayerConnectionInternal:SendMessage(String, Byte[], Int32)
UnityEngine.PlayerConnectionInternal:UnityEngine.IPlayerEditorConnectionNative.SendMessage(Guid, Byte[], Int32)
UnityEngine.Networking.PlayerConnection.PlayerConnection:Send(Guid, Byte[])
UnityEngine.TestTools.TestRunner.Callbacks.<SendDataRoutine>c__Iterator0:MoveNext() (at C:\buildslave\unity\build\Extensions\TestRunner\UnityEngine.TestRunner\TestRunner\Callbacks\RemoteTestResultSender.cs:129)
UnityEngine.SetupCoroutine:InvokeMoveNext(IEnumerator, IntPtr)
[C:\buildslave\unity\build\Runtime/Network/PlayerCommunicator/GeneralConnection.cpp line 452]
(Filename: C:/buildslave/unity/build/Extensions/TestRunner/UnityEngine.TestRunner/TestRunner/Callbacks/RemoteTestResultSender.cs Line: 129)
Appears to be a problem when the player sends the results back to the editor at the end of a test run.
I didn't mark this as a Graphics Playmode Test package issue as although this package can reproduce the issue it doesn't seem specific to it but more an issue with sending a large amount of data back to the editor for the test results.
Relevant Slack thread for this https://unity.slack.com/archives/C0JHA6J4C/p1539116537000100
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- “Remove Unused Overrides” available on not loaded Scene and throws “ArgumentException: The scene is not loaded” warning
- Adaptive Probe Volume occlusion edge is calculated incorrectly when viewing probes near geometry edges
- Sampling a texture using an HLSL file throws shader errors and the code does not compile
- "Graphics.CopyTexture called with null source texture" error when Base Camera of an Overlay Camera is removed with DX11 Graphics API and Compatibility Mode enabled
- WebGL sends wrong value with large numbers when SendMessage function is used
Add comment