Search Issue Tracker
Fixed in 0.1.1-preview
Votes
0
Found in [Package]
0.1.0
Issue ID
1173318
Regression
Yes
Using TryDequeue on an empty NativeQueue stops the queue from receiving any new elements by using Enqueue
How to reproduce:
1. Open the attached "NativeQueue Test.zip" project
2. Open "SampleScene"
3. Enter Play mode and inspect the console
Expected results: The NativeQueue has 1 element after Enqueue is called for the second time
Actual results: The NativeQueue has 0 elements after Enqueue is called for the second time
Reproducible with: 2019.1.13f1, 2019.2.1f1, 2019.3.0a11 (Collections package version 0.1.0)
Not reproducible with: 2018.4.5f1, Collections package versions 0.0.9 - preview.12 and below
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
- Crash on PackageManager::DisplayErrorDialog when a Local Package path containing URI-encoded characters ('%20') fails to resolve
- [WebGL] Objects with a Shader Graph material that uses the Scene Depth node are not rendered
- “Always Included Shaders” list container border is missing when element count is manually set to 0 in Graphics Project Settings
- Crash on mono_traverse_object_internal when opening a specific Scene
- Animator parameters Bool, Trigger, and Int are not reset to default values when Animator.ResetControllerState(true) is called
Resolution Note (fix version 0.1.1-preview):
Thanks for submitting, we fixed it in `0.1.1-preview`.