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
- Performance Markers Search window shows an empty entry in the list
- Enabling Deep Profiling in Performance Markers Search window breaks Inspector panel buttons when navigating through the marker items
- Dragging selector from selector row background shows preview but does not apply class in UI Builder
- An "InvalidOperationException" error is thrown when TryRemoveItem is used with rebuildTree set to false
- Build fails with IL2CPP error when building on Android platform in a specific project
Add comment