Search Issue Tracker

Fixed in 2021.1

Fix In Review for 2019.4, 2020.1, 2020.2

Votes

0

Found in

Issue ID

1279213

Regression

No

Profiler - RawFrameDataIterator ThreadID will always return 0 for profiler frame data loaded from .data files

Profiling

-

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

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.