Search Issue Tracker
Duplicate
Votes
0
Found in
2017.3.0a1
2017.3.0f1
Issue ID
979361
Regression
Yes
Assertion failed on expression: 'm_currentEntriesPtr != NULL && m_IsGetingEntries' when opening script with Visual Studio
How to reproduce:
1. Open the attached "AssertionRepro" project
2. Go to "Scenes" folder and open "Levels" scene, enter playmode
3. Null Reference Exception error will appear in the console, double click on it to open the script that causes the error (make sure that Visual Studio would not be open before doing this)
Expected result: Script gets opened, no errors appear
Actual result: Script gets opened, "Assertion failed: Assertion failed on expression: 'm_currentEntriesPtr != NULL && m_IsGetingEntries'" assertion appears
Regression introduced in - 2017.3.0a1
Reproducible with - 2018.1.0b1, 2017.3.0p1, 2017.3.0a1
Not reproducible with - 2017.2.1p1
Notes:
1. Happens with Visual Studio 2017/2015, does not happen with Visual Studio Code or MonoDevelop
2. Assertions are thrown only when opening script by double clicking on the error, opening a script trough a Project window, does not seem to cause the assertions
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
This is a duplicate of issue #975044