Search Issue Tracker
Won't Fix
Won't Fix in 3.3.X
Votes
1
Found in [Package]
3.0.1-Hotfix
Issue ID
HUBX-743
Regression
Yes
Unity Hub crashes when running on Amazon EC2 Mac Instance
Steps to reproduce:
1. Run Mac on AWS (https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2-mac-instances.html)
2. Download and install Unity Hub (https://unity3d.com/get-unity/download)
3. Open Unity Hub
Expected result: Unity Hub opens
Actual result: Unity Hub crashes
Reproducible with: 3.0.1, 3.1.0-beta.1
Not reproducible with: 2.4.5
First few lines of the stacktrace:
Thread 0 Crashed:: CrBrowserMain Dispatch queue: com.apple.main-thread\\
0 com.apple.CoreFoundation 0x00007fff209bd775 CFStringGetCString + 57\\
1 com.github.Electron.framework 0x0000000101e2bc0c ElectronInitializeICUandStartNode + 29356\\
2 com.github.Electron.framework 0x0000000101e3a7e5 ElectronInitializeICUandStartNode + 89733\\
3 com.github.Electron.framework 0x0000000101e3a74f ElectronInitializeICUandStartNode + 89583\\
4 com.github.Electron.framework 0x0000000101e3a5e8 ElectronInitializeICUandStartNode + 89224\\
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
- Spot Light with 'Box' Shape stops working when it collides with Mesh
- Accepting Asset Store EULA endless loop in Package Manager window
- “InvalidOperationException: Sequence contains no matching element“ error when reenabling a custom Debug Draw Mode
- Prefab that contains a layout group is marked as changed by the Editor when opened
- Emission animation does not appear when the "Emission Map" parameter is set to black in a Lit material
Resolution Note:
There are no fixes planned for this Bug
Resolution Note (3.3.X):
Left a investigation report in the comments.
The issue seems to be a much more closely related to how chromium apps running in a headless mode behave on EC2 mac instances. The known workaround involves using dummy monitors or connecting to this instances via a screensharing software. To provide a Hub specific solution to this issue would involve an overhaul of the CLI experimental feature.