Search Issue Tracker
Fixed
Fixed in 1.8.8
Votes
0
Found in [Package]
1.8.4
Issue ID
BUR-2433
Regression
No
Burst Compiled Jobs are executed differently in Player and Editor when inspected with Profiler
How to reproduce:
1. Open the “BurstRepro“ project
2. Open the “SampleScene”
3. Open the Profiler (Window > Analysis > Profiler)
4. Enter Play Mode then wait 1-2 seconds and select a Frame in the Profiler
5. Expand and observe the “Job” section of the selected Frame
6. Exit Play Mode then enable “Development Build” and “Autoconnect Profiler” (File > Build Setting)
7. Build And Run then wait 1-2 seconds and exit the Player
8. Select a Frame in the Profiler
9. Expand and observe the “Job” section of the selected Frame
Expected result: Editor Play Mode and Player Burst Jobs have “MultiplyFloat3sByMultiplierJob” for each Worker thread which are displayed in a green color
Actual result: Editor Play Mode Burst Jobs have only “MultiplyFloat3sByMultiplierJob” for each Worker thread which are displayed in a green color while Player Burst Jobs have “MultiplyFloat3sByMultiplierJob” and “ExecuteJobFunction.Invoke()” for each Worker thread which are displayed in a blue color
Reproduced with: 1.6.6, 1.8.4 (2021.3.27f1), 1.8.7 (2021.3.27f1, 2022.3.4f1, 2023.1.2f1, 2023.2.0a21)
Reproduced on: Windows 11
Note: In 2021.3.27f1 the actual result is swapped
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Test Runner’s vertical scrollbar overlaps with the up and down arrows and upper toolbar tabs when the window is minimized
- The Input Field view is not updated when deleting lines of text
- The scrollbar does not respect empty lines in the Input Field
- “Texture Atlas Viewer“ button text overlaps another button when the UI Toolkit Debugger is narrowed
- Thresholds are no longer automatically calculated after deleting Motion fields in Blendtrees
Add comment