Search Issue Tracker
Fixed in 2019.1.X
Votes
0
Found in
2018.2.5f1
Issue ID
1073477
Regression
No
Setting .isReadable during OnXprocessTexture causes it to still be true and have memory overhead
Reproduction steps:
1. Open the attached project "AssetProcessorIssue.zip";
2. Observe Textures/Black does not have read/write enabled and also is 42.7 KB size;
3. Build the project for a Player;
4. Launch the build;
5. In the Unity, open Profiler window;
6. Choose a memory section, and in the detailed memory section, take a sample of the memory;
7. Observe the results of black texture size.
Actual results: the size of the Black texture takes up double the memory (85 KB), like what you would expect if read/write enabled is true.
Reproducible on: 2017.4.10f1, 2018.1.9f2, 2018.2.5f1, 2018.3.0a10.
Reproducible both with iOS, Android and OSX.
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
- [Vulkan] The memory allocation increases rapidly when there are multiple (three or more) Real-Time Reflection Probes in the Scene
- Addressables Profiles and Analyze windows no minimum window size
- [macOS] Library folder of the opened project can be deleted which leads to the crash
- “Default Scene” dropdown field contains a spelling mistake “Default Builtin”
- Editor crashes on PPtr<Mesh> after adding Text Mesh and Cloth Components to the same GameObject
Resolution Note (fix version 2019.1):
There was no code change, the issue was marked as Fixed because the Documentation was updated to remove the part that advised Users using .isReadable during the import process because it's not needed and actually harmful. However, the current behavior has not changed and the repro steps lead to the same results, which is expected.