ID:2913091
 
BYOND Version:514
Operating System:Windows 11 Home
Web Browser:Chrome 121.0.0.0
Applies to:Dream Daemon
Status: Open

Issue hasn't been assigned a status value.
Descriptive Problem Summary:
the Profiler reports higher self CPU than total CPU when a proc causes an infinite loop (Also I'm pretty sure this causes negative self CPU as well)
Numbered Steps to Reproduce Problem:
Profile your code
Cause an infinite loop
Look at the profiled code, the self CPU usage is higher than the total CPU usage
Code Snippet (if applicable) to Reproduce Problem:
mob/verb/cause_infinite_loop_verb()
name = "cause infinite loop"
cause_infinite_loop()

mob/proc/cause_infinite_loop()
cause_infinite_loop()


Expected Results:
Total CPU and self CPU are roughly the same in the profiler
Actual Results:
Total CPU is lower than the self CPU by a significant degree, sometimes it's even negative.
                         Profile results (total time)
Proc Name Self CPU Total CPU Real Time Overtime Calls
---------------------------------- --------- --------- --------- --------- ---------
/mob/proc/cause_infinite_loop 11.910 1.990 1.990 11.910 199
/mob/verb/cause_infinite_loop_verb 0.000 0.010 0.010 0.000 1

Does the problem occur:
Every time? Or how often? Yes
In other games? Yes
In other user accounts? Yes
On other computers? Yes

Did the problem NOT occur in any earlier versions? If so, what was the last version that worked? (Visit http://www.byond.com/download/build to download old versions for testing.) Unaware if it ever didn't occur, still happens in 515 as well.