Search Issue Tracker
Not Reproducible
Votes
3
Found in
2018.2.0a1
2018.2.0a5
2018.2.0b1
Issue ID
1026784
Regression
Yes
[macOS]"Assertion failed on expression: 'ptr == NULL || ..." error printed in the Console window while building the app
Steps to reproduce:
1) Download attached project and open in Unity
2) Make sure platform is set to Android/iOS in the Build Settings
3) Press Build button
Observe the Console window, you will see an error printed in the Console window during the building process:
Assertion failed on expression: 'ptr == NULL || !HAS_ROOT_REFERENCE(GET_CURRENT_ALLOC_ROOT_REFERENCE()) || GET_CURRENT_ALLOC_ROOT_REFERENCE() == GET_ROOT_REFERENCE(s_MonoDomainContainer, kMemMono)'
UnityEngine.GUIUtility:ProcessEvent(Int32, IntPtr)
Reproduced with:
2018.2.0a7, 2018.2.0b1
Not reproduced with:
2018.1.0b11, 2018.1.0f1
Regression since:
Somewhere between 2018.2.0a1-2018.2.0a5
Can't check with 2018.2.0a5 and lower, because of PackageManager errors
Note: There is no error using Windows 10 machine
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
- [Mobile] Developer Console does not appear when an error is thrown
- [HDRP] Game view renders artifacts when Camera's Component "Post Anti-aliasing" is set to "TAA" and Dynamic Resolution's "Forced Screen Percentage" is changed
- A deactivated Prefab's name color becomes white when a GameObject in the scene is deactivated
- The Game view becomes blank when using Frame Debugger with MSAA and Texture binding enabled in Play Mode
- NullReferenceException is thrown when changing the Inspector preview selection
OneManArmy3D
Sep 20, 2018 20:58
Also in 2018.1.9f1
jimmy12day
Sep 11, 2018 20:22
Reproduced in 2018.1.6f
daisySa
May 22, 2018 05:06
Also seeing this on Windows 10 with 2017.4.3f1.
Killersan
May 14, 2018 09:00
The same issue occurs for 2018.1.0f2 on windows standalone platform during the build process.
Steel-Heart-Games
May 04, 2018 12:12
Same thing with custom build script on 2018.1.0f2
JonBPS
May 03, 2018 14:48
I am seeing this in the 2018.1.0f2 release when doing android builds using a custom build process.
Seems harmless as the builds complete fine but would like to know why it's happening.