Search Issue Tracker
Fixed
Fixed in 1.5.x
Votes
0
Found in [Package]
1.5.4
Issue ID
LOC-1213
Regression
No
Localized String never stops existing when StringChanged is subscribed to
Reproduction steps:
1. Open the attached “IN-101536.zip” project
2. Open the “SampleScene”
3. Enter Play mode
4. Observe the Console
Expected result: Each value change should trigger exactly one callback event
Actual result: Each new LocalizedString creation adds another callback subscription that persists, resulting in an increasing number of duplicate callbacks (e.g., value 5 triggers 6 callbacks, value 6 triggers 7 callbacks, etc.)
Reproducible with: 1.4.5 (2022.3.62f1) 1.5.4 (2022.3.62f1, 6000.0.48f1, 6000.1.3f1, 6000.2.0b1)
Reproducible on: Windows 10 (User reported), Windows 11
Not reproducible on: no other environment tested
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- UI Text color is incorrect when text is rendered on SubMeshUI
- "Invalid SortingGroup index set in Renderer" errors when making many modifications in same frame
- Crash on GizmoBufferSizeHistory::GetBuffer() when opening a specific scene
- RenderTexture is not initialized when it is set as Material's Texture
- Branch node outputs a random value instead of a constant on the false conditon
Add comment