Code profiler sometimes returns incorrect value for real time in Bug Reports

ID:112908
 
May 6 2011, 5:08 pm
Resolved
Profiling code sometimes returned incorrect values of real time for certain procs.
BYOND Version:481
Operating System:Windows XP Pro
Web Browser:Firefox 3.5.19
Applies to:Dream Daemon
Status: Resolved (482)
This issue has been resolved.
This is a very old bug and has been reported by many users.

Descriptive Problem Summary:
Some procs return nonsensical values for their real running time.

Numbered Steps to Reproduce Problem:
While a proc is sleeping, turn on profiling.

Code Snippet (if applicable) to Reproduce Problem:
proc/Looper()
  while(1)
    ...
    sleep(10)


Expected Results:
Real time should start at 0 when profiling is turned on.

Actual Results:
Real time is not initialized.