Search Issue Tracker
Fixed in 2018.1.X
Votes
6
Found in
2017.3.0a1
2017.3.0f1
Issue ID
975044
Regression
Yes
When leaving play mode error Assertion failed on expression: 'm_CurrentEntriesPtr != NULL && m_IsGettingEntries' is thrown
Steps to reproduce:
1. Download 975044_repro.zip and open "test" scene
2. Enter play mode
3. Double click on here message in Console
4. Wait until visual studios open
5. Exit play mode
6. Assertion failed error appears.
Expected results: No errors is thrown to Console
Actual results: Assertion failed error is thrown to Consol
Full error:
Assertion failed: Assertion failed on expression: 'm_CurrentEntriesPtr != NULL && m_IsGettingEntries'
UnityEngine.GUIUtility:ProcessEvent(Int32, IntPtr)
Note: This issue doesn't reproduce on OSX
Reproduced with: 2018.1.0a7, 2017.3.0f2, 2017.3.0a1
Not reproducible with: 2017.2.0p4
Regression introduced in: 2017.3.0a1
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
- Scene view audio toggle doesn't work after disabling and enabling audio source component with audio random container
- Pitch changes while paused messes up scheduling of the audio random container
- Crash on detail::ComputeShaderSnippetKey when entering the Play mode
- Unable to interact with Material Inspector window when creating a new Material and renaming it
- Shadow artifact is cast onto GameObjects in the Scene view when the Scene view lighting is disabled
muh2k4
Apr 24, 2018 14:12
Thanks! Your comment helped me a lot. In my situation this errormessage produced a major lag. When I skip a frame before playing the second video, the error disappears.
rad1c
Mar 26, 2018 09:46
2017.3.1
Trying to play two video clips in a row with VideoPlayer component:
Assertion failed: Assertion failed on expression: 'info.videoAudioData == NULL'
(setting audio source/target/etc properly, so there shouldn't be any issues. tried to recreate Library folder/data, same result)