Search Issue Tracker
Won't Fix
Won't Fix in 6000.3.X
Votes
0
Found in
2022.3.66f1
6000.0.58f1
6000.2.5f1
6000.3.0b2
Issue ID
UUM-117614
Regression
No
Memory leak warnings are constantly thrown when Generating Font Atlas in Font Asset Creator with 4096x8192 Atlas Resolution
Steps to reproduce:
- Create a new Unity project using the Universal 3D template
- Import the provided Font in the Attachments
- Open the Font Asset Creator window (Window > Text > Font Asset Creator)
- Dock the Font Asset Creator window
- Select the imported Font as the Source Font
- Change Atlas Resolution to 4096x8192
- Generate Font Atlas
- While the Font Atlas is being generated, resize the docked Font Asset Creator window
- Observe the Console window
Actual results: Memory leak warnings are thrown
Expected results: No errors or warnings are thrown
Reproducible with versions: 2022.3.66f1, 6000.0.58f1, 6000.1.16f1, 6000.2.5f1, 6000.3.0b2
Tested on (OS): macOS Silicon Sequoia 15.6.1
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
- Error “Shader error in 'YSCloudCover': call to 'tex3D' is ambiguous at Assets/YSCloudCoverText.shader(606) (on d3d11)“ is present when compiling tex3D shader with DXC
- Placeholder asset is not loaded with Advertisement Legacy sample when using the latest version of the package
- Addressables content build fails but the Player build is successful when building a development build
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
Resolution Note:
It's a legitimate bug but falls below the threshold for us to fix in the foreseeable future. Note, in general, the Font Asset Creator window is very low priority for us to improve, and that unfortunately includes minor fixes like this one. We will of course fix major issues like crashes.
Also, the Font Asset Creator window will be significantly when we remove TextCore and switch everyone to ATG.
Resolution Note (6000.3.X):
It's a legitimate bug but falls below the threshold for us to fix in the foreseeable future. Note, in general, the Font Asset Creator window is very low priority for us to improve, and that unfortunately includes minor fixes like this one. We will of course fix major issues like crashes.
Also, the Font Asset Creator window will be significantly when we remove TextCore and switch everyone to ATG.