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
- Profiler disconnects from WebGL Player when it gets clicked on in URP
- Crash on -[NSApplication _crashOnException:] when opening a specific custom Editor window
- Sprite editor does not allow creating new sprite tiles in a sprite sheet with a specific name
- Crash on block_locate_free when rendering a specific scene
- A submenu disappears on MacOS when the MenuItem method argument "isVariableFunction" is set to "false" and priority argument is set to "-1"
Add comment