Search Issue Tracker
Won't Fix
Votes
1
Found in
5.0.0f3
Issue ID
676743
Regression
Yes
HashSet.RemoveWhere does not correctly evaluate null for GameObjects in builds
To reproduce:
1. Open attached project
2. Open test scene
3. Press play
4. Press "n" to remove numbers from the Numbers HashSet
5. Press "s" to add a null to the Strings HashSet and then filter out nulls
6. Press "d" to delete a GameObject referenced by the SceneObjects HashSet
7. Press "o" to filter out nulls.
8. Build and run standalone build
9. Repeat steps 4-7
8. Notice that nulls doesn't filter out and the HashSet will always be at 3 elements
Comments (3)
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
- Multiple errors occur when setting the Render Object Event to AfterRenderingPostProcessing while using STP for Upscaling
- UnityYamlMerge.exe doesn't correctly handle merge conflicts in modified properties on a prefab variant
- Inconsistent color scheme in "Details" section of "Select Presets" inspector window
- Crash on __pthread_kill when launching Editor via command-line with "-disableManagedDebugger" argument
- [VFX] Deleting “New Group Node” name doesn’t allow to type or add new name
robert-ferrese
Jan 05, 2016 05:16
Is there a way to remove null objects from a hash set that does work in a windows standalone build?
anderbubble
Jul 31, 2015 05:19
Why is this wont fix? I just spent over an hour tracking this down myself.
jpthek9
Apr 24, 2015 05:34
I'm not sure if this is Unity-specific, but I'm having this problem too.