Search Issue Tracker
Not Reproducible
Votes
0
Found in
2019.2.0a1
2019.3.0a1
2019.3.0a8
Issue ID
1168790
Regression
No
[Linux] NullReferenceException when trying to enable Linux x86_x64 through Platform settings of a Managed DLL
How to reproduce:
1. Open the attached project 'unity.zip'
2. Select BurtCommon.dll in the Project window, make sure the Inspector tab is open
3. Tick the Linux x86_64 Platform in the Platform settings (un-tick it if it was ticked in the first place)
4. Click 'Apply'
Expected results: Linux x86_64 platform gets enabled
Actual results: Linux x64_64 is still disabled, NullReferenceException in the console
Reproducible with: 2019.1.9f1, 2019.2.0b9, 2019.3.0a5
Reproduced on CentOS which can't run versions past 2019.3.0a5.
Full error:
NullReferenceException: Object reference not set to an instance of an object
UnityEditor.Experimental.AssetImporters.AssetImporterEditor.InternalSetTargets (UnityEngine.Object[] t) (at /home/builduser/buildslave/unity/build/Modules/AssetPipelineEditor/ImportSettings/AssetImporterEditor.cs:122)
UnityEditor.Editor.OnForceReloadInspector () (at /home/builduser/buildslave/unity/build/Editor/Mono/Inspector/Editor.cs:603)
Note: In 2019.3.0a1 instead of the NullReferenceException there are these errors:
Assertion failed on expression: 'targetHash.IsValid()'
Assertion failed on expression: 'loadedImportedAsset.targetHash.IsValid()'
Note 2: In 2019.2.0a1 and in 2019.1.9f1 it seems to work but there is another error in the console:
Win32Exception: ApplicationName='/run/media/pauliusg/Storage/Unities/2019.2.0a1/Editor/Data/Tools/RoslynScripts/unity_csc.sh', CommandLine='/noconfig @Temp/UnityTempFile-b69cd5a42947ef0768bc53765acb3b33', CurrentDirectory='', Native error= Out of memory
Note 3: Could not test in 2019.1.0a1 and in earlier version due to Platform settings not existing.
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
- “FMOD failed to set the software format to the custom sample rate…” warnings are thrown as System Sample Rate value is being changed in Audio section of Project Settings window
- VFX Marquee selection does match the visual indicator
- “Invalid AABB aabb” errors are spammed when “Infinity” value is entered in Collider Component fields
- Editor Role does not sync with the MPPM Play Mode Scenario Role when entering Play mode
- Long asset names cause overlap with the “Find” function in search result tabs
Resolution Note (2020.1.X):
Unity changed some tooling recently and this bug no longer reproduces on CentOS 7 in 2019.4+.