Search Issue Tracker
Fixed in 2021.1.X
Fixed in 2019.4.X, 2020.1.X, 2020.2.X
Votes
0
Found in
Issue ID
1279213
Regression
No
Profiler - RawFrameDataIterator ThreadID will always return 0 for profiler frame data loaded from .data files
Repo:
1. Open the profiler and capture a bunch of frames
2. Save the capture
3. Load the capture
4. use RawFrameDataAPI to loop over threads
eg:
int frameIndex = 0;
int threadIndex = 0;
const int maxFrames = 300;
while(frameIndex < maxFrames)
{
while(true)
{
using (RawFrameDataView frameData = ProfilerDriver.GetRawFrameDataView(frameIndex, threadIndex))
{
if (!frameData.valid)
break;
Debug.Log(frameData.threadId);
}
threadIndex++;
}
}
Expected: threadId is 0 only once for main thread
Actual: threadId always returns 0
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Warning icon is cut off and misplaced in Inspector when selecting a Shader with a compiler warning
- AI Navigation Sample Scenes do not work and throws “InvalidOperationException”, “Curl error3”, “CrashReporter”, and “NullReferenceException” errors when using the new Input System Package (default) on a new project
- Bottom of Build Size window in Project Auditor becomes inaccessible when a monitor has a high display scaling
- AI Assistant fails to load account information when AI assistant is opened
- [Linux] Improve "GPUResidentDrawer" warning message to include actionable guidance when creating a new Unity project using Universal 3D Template
Add comment