| Commit message (Collapse) | Author | Files | Lines |
|---|
|
|
|
|
|
|
|
and number of active threads ( at least when a pool is in use)
|
|
issues
|
|
|
|
|
|
|
|
the resolution avaiable for StopWatchs. Value in double since it can be large (as machine uptime in high resolution ticks)
|
|
|
|
|
|
logging
If the XML was truncated for some reason then ExecuteReadProcessors() would get into an infinite loop, using high CPU. Now it detects EOF (and several other error cases) and aborts.
The rest of the changes just improve logging of XML in case of errors, so that we can see what the bad XML is.
|
|
Another change: removed the second call to userManager.AddUser(). UserManagementModule won't modify an existing record.
|
|
|
|
Signed-off-by: Diva Canto <diva@metaverseink.com>
|
|
|
|
libraries.
|
|
|
|
This shows named threadpool calls (excluding timer and network calls) that are currently queued or running.
Also shows total of labelled and any anonymous calls.
|
|
problem diagnosis.
"show threadpool calls" now also returns named (labelled), anonymous (unlabelled) and total call stats.
|
|
smartthreadpool calls
|
|
maximum and increase the idle time before release to OS
|
|
a threadpool) via Watchdog.RunInThread() rather than Util.RunThreadNoTimeout()
The functionality is the same but this allow us to monitor such tasks via "show threads" and abort them for test purposes, etc.
Also extends thread names to provide more info (e.g. SendInitialDataToClient says what client the task is for).
|
|
This was previously effectively being done by XmlDocument in the multiple passes through the XML.
This change tells XmlReader to ignore whitespace. This also means changing arguments to use XmlReader instead of XmlTextReader (a descendent of XmlReader) directly.
XmlReader.Create() has been the recommend way to create XML readers since .NET 2.0 as per MS SDK and is the only way to specific ignore whitespace settings.
|
|
|
|
"Queue threadfunc" for a particular thread then don't log "Run threadfunc" or "End threadfunc" for that thread either.
|
|
|
|
As per http://msdn.microsoft.com/en-us/library/system.random%28v=vs.100%29.aspx, the .NET Random class is not thread-safe.
If called by multiple threads at once, methods may return 0.
Except for llRand(), other OpenSimulator code did not lock before calling a shared Random instance.
This commit adds a ThreadSafeRandom class that extends Random but does internal locking so that it is thread-safe.
This change is invisible to existing callers and the explicit locking in the llFrand() implementation is now redundant.
|
|
shutdown.
Adds regression test for this case.
|
|
config option, LogOverloads, to log when a thread pool overload occurs.
This option defaults to "True" because the logging data is useful for
diagnosing threading issues.
|
|
No one needs to see every thread launch.....
|
|
list of assets exist.
This method is used to optimize sending assets with embedded assets: e.g., when a Hypergrid visitor takes an item into the inventory.
|
|
- Changed a few places that launch long-lasting threads to skip the timeout altogether
|
|
- MemoryBuffer isn't seekable, so we can't log it. Log the string instead.
- Handle compressed streams
- Don't attempt to dump binary data. Either don't log it at all (if we know it's binary), or at least convert non-ASCII characters to ASCII.
- Log responses to HTTP requests
- Use the same log prefix for all of these log messages ("[LOGHTTP]"), to make them easy to see at a glance
- Increased the snippet length to 200 (80 doesn't show enough), and add "..." only if the message was actually truncated
Resolves http://opensimulator.org/mantis/view.php?id=6949
|
|
|
|
(which has a 1-minute timeout)
Resolves http://opensimulator.org/mantis/view.php?id=6945
|
|
threadpool level" to set the logging level.
Resolves http://opensimulator.org/mantis/view.php?id=6945
|
|
If a task in the thread pool hangs then it will permanently take up
one of the threads. If this happens repeatedly then the thread pool will
become exhausted and OpenSim will fail. This watchdog terminates threads in the
thread pool that have been executing for over a minute (which probably
means they're hung).
Resolves http://opensimulator.org/mantis/view.php?id=6945
|
|
packet type
Resolves http://opensimulator.org/mantis/view.php?id=6945
|
|
Resolves http://opensimulator.org/mantis/view.php?id=6945
|
|
Resolves http://opensimulator.org/mantis/view.php?id=6945
|
|
threadpool.
Resolves http://opensimulator.org/mantis/view.php?id=6945
|
|
"CreatorData" field is calculated, to ensure uniformity
Resolves http://opensimulator.org/mantis/view.php?id=6933
|
|
Recent versions of Firestorm and Singularity have started sending the viewer name in the 'Channel' field, leaving only their version number in the 'Viewer' field. So we need to search both of these fields for the viewer name.
This resolves http://opensimulator.org/mantis/view.php?id=6952
|
|
This reverts commit 52b7b40034ddbb21d06b11ddc4eb6d766b0f616d.
Got the semantics wrong - the sempahore is required so that the blocking thread waits for a signal.
|
|
Exclusion is already guaranteed by the lock on m_syncRoot.
Semaphore could not allow more than one thread in these sections anyway since the underlying SDK structures are not thread-safe.
|
|
thread-safe operation
|
|
|
|
XmlRpcGroupsServiceConnector error
|
|
|
