[Bug] Lua profiler scopes not working correctly #510
D4isDAVID
started this conversation in
[BUG] FiveM for GTAV Enhanced
Replies: 1 comment
|
Some important context I forgot to mention, the profiler records like every single function call, so when running a lot of code the recording will be crazy huge and riddled with all of the function calls. |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Summary
Profiler scopes in Lua don't seem to be registering correctly, spanning from the middle to the end of a
ProfilerEnterScopecall, rather than ending at aProfilerExitScopecall.Issue type
Both / Unsure
Repro rate
Always
Server build version
139
OS
No response
CPU
No response
GPU
No response
RAM
No response
Storage type
None
Connection type
None
ISP and bandwidth
No response
DxDiag
No response
Network graph
No response
Platform
None
OS version / distribution
No response
CPU
No response
RAM
No response
Using txAdmin?
None
Hosting provider
None
Machine type
None
/perf endpoint output
No response
DDoS protection
No response
ulimit -n value (Linux only)
No response
Docker Compose file (Docker only)
No response
Steps to Reproduce
profiler_scope_test.zip
profiler record 100, and runprofiler_scope_testimmediately after.profiler viewto see the profiler recording.test.Expected Behavior
The scope should look similar to this and other runtimes, as in Legacy:

Actual Behavior
The scope only lasts up to the end of the

ProfilerEnterScopecall.Evidence
profileData_legacy.json
profileData_enhanced.json
Additional Context
No response
All reactions