Overtime Feature Giving Crazy Values

ID:2444891
 
Mar 28 2019, 2:45 pm (Edited on Mar 28 2019, 3:01 pm)
Resolved
The overtime column of the profiler didn't clear properly when reading data from servers before 512.1465, so it showed junk data instead of the expected 0.
BYOND Version:512.1465
Operating System:Windows 10 Home 64-bit
Web Browser:Chrome 73.0.3683.86
Applies to:Dream Seeker
Status: Resolved (512.1466)
This issue has been resolved.
Descriptive Problem Summary:

Version 512.1465

The new Overtime Profiler column outputs crazy high numbers or values like -1.#QO

Numbered Steps to Reproduce Problem:

Load a game of SS13. Or any other BYOND game with high processing, potentially.
Open the Profiler
Refresh and you'll get crazy values

Image Gallery
Images were taken under high load.
https://i.imgur.com/BjkII3y.png
https://i.imgur.com/6YIgnos.png
https://i.imgur.com/Z6107cO.png
https://i.imgur.com/y6AecnZ.png


Expected Results: Numbers that make sense.

Actual Results: Either all 0 value or nonsensical scaling ones.

Does the problem occur:
Every time? Or how often? Roughly 30% of Refreshes
In other games? Not Tested
In other user accounts? Yes
On other computers? Yes

When does the problem NOT occur? Every now and then, and there's no overtime values then.

Did the problem NOT occur in any earlier versions? If so, what was the last version that worked? Feature did not exist.

Workarounds: None

Edit: Moved to Bug Reports since 512 is now on stable.
Mar 28 2019, 3:03 pm
Yep, I saw this too. Looks like the problem is when connecting to older servers that don't report OT, where it should be 0. It'll be fixed in the next release.
Mar 29 2019, 9:12 am
Lummox JR resolved issue with message:
The overtime column of the profiler didn't clear properly when reading data from servers before 512.1465, so it showed junk data instead of the expected 0.