Search Issue Tracker
Fixed in 2022.3.9f1
Fixed in 2022.3.X, 2023.1.X, 2023.2.X, 2023.3.X, 7000.0.0a1, future release
Votes
0
Found in
2022.3.7f1
2023.1.8f1
2023.2.0b4
2023.3.0a2
Issue ID
UUM-45483
Regression
Yes
"Top level scope allocation is permitted only on the main thread." error thrown when using Allocator.Temp
Reproduction steps:
1. Open the attached project "NativeAllocationIssue-2023.1"
2. Enter Play mode
Expected result: no errors in the Console
Actual result: "Top level scope allocation is permitted only on the main thread." and "ArgumentException: Could not allocate native memory." errors in the Console
Reproducible with: 2023.2.0b1, 2022.3.7f1, 2023.1.8f1, 2023.2.0b4
Not reproducible with: 2023.2.0a23
Could not test with: 2021.3.29f1 (compilation errors)
Reproducible on: macOS 13.4.1 (Intel), Windows 10 (user’s)
Note: not reproducible when using Allocator.Persistent or Allocator.TempJob
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 MarkAllDependencies when opening scenes with Assets from the YarnSpinner package
- Crash on CollectAllSceneManagerAndObjectIDs when opening a specific Scene
- GPU device suspended error when replaying a video in the Video Player with NVIDIA Vertical Sync set to Fast
- GPU device suspended error when replaying a video in the Video Player with NVIDIA Vertical Sync set to Fast
- SetComponentEnabled uses class instead of struct when constraining Enableable Component type
Add comment