Search Issue Tracker
Postponed means that the issue was either a feature request or something that requires major refactoring on our side. Since that makes the issue not actionable in the close future we choose to close it as Postponed and add it on our internal roadmaps and technical debt pages instead.
Postponed
Votes
1
Found in
2018.2.1f1
Issue ID
1065611
Regression
No
[Job System] Using Allocator.Persistent causes JobTempAlloc error in the console
Reproduction steps:
1. Open the attached project "Persistent.zip";
2. Open the SampleScene;
3. Make sure that "Use Jobs" is checked under the Main Camera object;
4. Enter a play mode.
Expected results: The script will be executed without any errors.
Actual results: The script throws an error in the console:
Internal: "JobTempAlloc has allocations that are more than 4 frames old - this is not allowed and likely a leak"
Reproduced on: 2018.1.9f1, 2018.2.4f1, 2018.3.0a8.
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
- Crash on GizmoDrawingPhysics2D::DrawCompositeCollider2DGizmo when opening a Scene that has corrupted GameObjects with Tilemap Components
- Scrolling vertically and horizontally is very fast when in Play Mode and RuntimeInputBackend is set to UIToolkitInputBackendOption.Default
- Crash on MemoryProfiler::UnregisterAllocation when initializing entities and leaving Play Mode with Occlusion Culling enabled
- Crash on mdb_page_alloc when opening a project that was running while the PC shut down
- macOS Player freeze when using RunInBackground and Command+Tabbing to and from the application
Resolution Note:
Long running jobs without this warning not currently supported. Do expect to support in the future, however.