| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
| |
with other monitoring code from OpenSim.Framework
|
| |
|
|
|
|
|
|
| |
region console "show stats" command
This aims to capture the amount of memory that OpenSim turns over whilst operating a region.
This memory is not lost - apart from leaks it is reclaimed by the garbage collector.
However, the more memory that gets turned over the more work the GC has to do to reclaim it.
|
| |
|
|
|
|
| |
timer setting.
This is to help detect situations where thread timeout warnings are being generated because of general machine issues rather than deadlock, network or other problems.
|
| |
|
|
| |
to reflect what it actually is
|
| |
|
|
|
|
|
| |
timeout is breached.
This alarm can then invoke this to log extra information.
This is used in LLUDPServer to show which client was being processed when incoming and outgoing udp watchdog alarms are triggered.
|
| |
|
|
| |
This is how it was originally. This stops a very long running alarm callback from causing a problem.
|
| |
|
|
| |
returns and for consistency.
|
| |
|
|
|
|
|
|
| |
On the first frame, all startup scene objects are added to the physics scene.
This can cause a considerable delay, so we don't start raising the alarm on scene loop timeouts until the second frame.
This commit also slightly changes the behaviour of timeout reporting.
Previously, a report was made for the very first timed out thread, ignoring all others until the next watchdog check.
Instead, we now report every timed out thread, though we still only do this once no matter how long the timeout.
|
| |
|
|
| |
This also adds time since started to "show threads". Unfortunately these two changes got mixed in.
|
| | |
|
| | |
|
| |
|
|
| |
Hopefully this wil make "WATCHDOG: Asked to update thread ## which is not being monitored" messages." go away.
|
| |
|
|
|
|
| |
today in 8a0a78c.
Also adds these to the watchdogs with very large timeouts (should really be infinite)
|
| |
|
|
| |
This also changes the point of registration to the StartThread() call rather than the first Update()
|
| | |
|
| |
|
|
|
|
| |
abort a watchdog managed thread.
This is for diagnostic purposes.
|
| |
|
|
| |
OpenSim.Framework.Watchdog
|
| |
|
|
|
|
| |
track threads once the first call to UpdateThread() has been made, and allow re-tracking of threads that timed out but revived later
* Added a commented out call to Watchdog.UpdateThread() in OdeScene. If it turns out that loading a large OAR file or some other operation is timing out the heartbeat thread, we'll need to uncomment it
|
|
|
use Watchdog.StartThread(). While your thread is running call Watchdog.UpdateThread(). When it is shutting down call Watchdog.RemoveThread(). Most of the threads in OpenSim have been updated
|
