Search Issue Tracker
Fixed in 2017.3.0f3
Fixed in 5.6.X, 2017.1.X, 2017.2.X
Votes
0
Found in
5.6.2p3
Issue ID
932027
Regression
Yes
[Linux][AWS] Unity builds that are built on AWS crash on start
Unity builds that are built on Amazon Web Services node crash on start
Steps to reproduce:
1. Set up an AWS instance. (I've used a node with NVidia GRID K520 on Ubuntu 14.04, likely to be reproducible with Tesla K80 as well)
2. Install an X server with a virtual monitor (Guidelines are under paragraph "Run Unity app with graphics on Amazon Cloud!" in this article: https://medium.com/towards-data-science/how-to-run-unity-on-amazon-cloud-or-without-monitor-3c10ce022639 )
3. Install Unity and use it to build an empty project to Standalone Linux 64-bit
4. Open the executable on AWS machine.
Result: crash
Reproduced with: 2017.1.0f3, 2017.2.0b2
Did not reproduce with: 5.5.3f1, 5.6.2f1
Notes:
- Builds made on a local machine running Linux 17.04 did not reproduce crashes with any Unity version
- Builds made on a local machine running macOS 10.12.5 did not reproduce crashes with any Unity version
_______
Workaround: removing the libxrandr2 package from the machine that needs to run the player (although this will make it impossible to run the editor, because gtk requires xrandr).
Comments (1)
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
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
- Changing Transform values in Search window Inspector loses focus while dragging and stopping mouse without releasing dragging action
- Saving changes on the dirty VFX Graph during the Play mode throws "The referenced script (Unknown) on this Behaviour is missing!" warnings
- VFX Graph Debug Info overlaps the "Initialize" block debug info by default
sunyangsecbase
Sep 27, 2017 18:18
Hi Unity support team,
According to Raul Oses, this issue supposed to be fixed in 5.6.3p2: https://support.unity3d.com/hc/en-us/requests/131144
But I could not find any fix from recent 5.6 patches.
Could you please let us know when it will be fixed?
Thanks,
Yang