Debugging Timers (Getting core dumped when servers been running for a while) - Printable Version

+- SA-MP Forums Archive (https://sampforum.blast.hk)
+-- Forum: SA-MP Scripting and Plugins (https://sampforum.blast.hk/forumdisplay.php?fid=8)
+--- Forum: Scripting Help (https://sampforum.blast.hk/forumdisplay.php?fid=12)
+--- Thread: Debugging Timers (Getting core dumped when servers been running for a while) (/showthread.php?tid=653700)

---

Debugging Timers (Getting core dumped when servers been running for a while) - JMCortinax - 10.05.2018

As title, I'm hoping to debug all my timers as I think it's one of them that keeps causing my server to "crash" after it's been running 5-10 days. I get no errors in the sa:mp log or even crash detect other than my VPS saying "CPU time limit exceeded (core dumped)"

Is there an easy way to see what timers are running at one time or should I create a new log with timestamps and get each timer to print 1 or 0 each time it's running. I know it'll get spammy but at least it might narrow it down?

Either that or any other ideas on the CPU time limit error? Can't seem to get many search yields on the error specifically for SA:MP. I guess there's a major flaw somewhere in my code?

---

Re: Debugging Timers (Getting core dumped when servers been running for a while) - Dayrion - 10.05.2018

This plugin is made for: https://github.com/Zeex/samp-plugin-profiler

---

Re: Debugging Timers (Getting core dumped when servers been running for a while) - JMCortinax - 10.05.2018

Thank you for the reply, I'll try this out!

---