Closed winstliu closed 8 years ago
You running a fork?
Why would I of all people be running a fork?
More errors reported in #399:
L 06/03/2016 - 17:12:17: [SM] Native "KillTimer" reported: Invalid timer handle a6253cdb (error 3)
L 06/03/2016 - 17:12:17: [SM] Displaying call stack trace for plugin "freak_fortress_2.smx":
L 06/03/2016 - 17:12:17: [SM] [0] Line 1546, C:\50DKP\FF2\addons\sourcemod\scripting\freak_fortress_2.sp::DisableFF2()
L 06/03/2016 - 17:12:17: [SM] [1] Line 1426, C:\50DKP\FF2\addons\sourcemod\scripting\freak_fortress_2.sp::OnMapEnd()
(this is 1.10.9 so the line numbers are a bit off from stable)
Could the problem be here since we're only setting the timer to INVALID_HANDLE if the client is valid?
I think KillTimer does that, but either way, it's supposed to be given INVALID_HANDLE
I've never tried it, but maybe have it =-1 or =null? Not even sure you can give it any other value
null is 1.7's syntax for INVALID_HANDLE, no?
null is 1.7's syntax for INVALID_HANDLE, no?
More like delete <handle>
which kills the timer/closes the handle and sets it to INVALID_HANDLE/null.
Once the test server gets fixed I'll try some theories out.
Not seeing this anymore with the above commit. Assuming fixed? Hopefully?
Getting a few of these:
Not sure how this is happening.