Search Issue Tracker
Won't Fix
Votes
0
Found in [Package]
2.0.0 - preview.3
Issue ID
1229218
Regression
Yes
"Internal: JobTempAlloc has allocations that are more than 4 frames old" when a GameObject containing a SpriteSkin is disabled
How to reproduce:
1. Open user-submitted project (SpriteSkinBugRepo.zip)
2. Enter Play Mode
3. Wait a couple of seconds for the Sprite to get moved to the side of the screen and set inactive
4. See the Console window
Expected result: no warnings or errors are thrown
Actual result: Internal: JobTempAlloc warnings are thrown
Reproducible with: 2018.4.22f1
Not reproducible with: 2019.3.12f1, 2020.1.0b8, 2020.2.0a9
Could not test with: 2017.4.40f1(package unavailable)
Reproducible with package versions: 2.0.0 - preview.1, 2.0.0 - preview.3
Not reproducible with package versions: 1.0.16 - preview.2, 3.2.1, 4.2.2
Could not test with: 2.1.0 - preview.2, preview.2 - 2.2.1 (upgrading the project to 2019.1/2019.2 breaks the sprite setup)
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
- Objects with Universal Render Pipeline/Particles/Lit shader are always lit up when changing their Rendering Layer Mask
- PolySpatial “Trying to set shader on a Material Variant.” error is printed in the console when entering Play Mode
- 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
Resolution Note:
Closing the issue as won't fix since the package was in experimental and has been deprecated with the verified version for 19.3