| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
| |
in the wrong order, and the other because it NEEDS the inventory service set up. Test-writers, please please please do the scene setup properly EVERYWHERE. It's close to impossible to rely on tests that don't setup resource service references!
|
|\ |
|
| | |
|
| | |
|
| |\ |
|
| | |
| | |
| | |
| | |
| | |
| | | |
randomly occurs.
* LongVersion nIni may be causing the test thread death. Pausing OpenSimulator during startup causes a nIni error that makes debugging startup operations difficult for users. It might be because when it's in pause mode, something else reads from the nini config passed? If it is, it might not be fixable.. however, if it's concurrency that causes nini death it would make sense to give each section of the tests a new IConfigSource so that they don't read from the same configsource at the same time.
|
| | |
| | |
| | |
| | | |
UUID.
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | | |
and a lot of cleaning.
|
|\ \ \
| | |/
| |/|
| | | |
inventory-connector
|
| | | |
|
| |/
| |
| |
| | |
Handler - ref mantis #4010
|
| | |
|
| | |
|
|\ \
| |/ |
|
| |
| |
| |
| | |
* also re-trigger panda
|
| |
| |
| |
| | |
* Also re-trigger Panda.
|
| |
| |
| |
| | |
* also re-trigger panda
|
| |
| |
| |
| | |
inside a try/Catch (ThreadAbortException) to try and get around scene code aborting the testing thread. Use a Messenger class to report the results back to the test thread.
|
|\ \
| |/ |
|
| |
| |
| |
| | |
creating the circuitdata object to see if it's the cause of a null reference exception in the TestAddNeighbourRegio test
|
| | |
|
| |
| |
| |
| | |
starting to get on my nerves.
|
| | |
|
|\ \
| |/ |
|
| | |
|
|/
|
|
| |
Redirection of the RootFolder property is still todo. This compiles but probably inventory will be inconsistent.
|
|
|
|
|
|
|
| |
starting to work! - but can't be activated incrementally, the flip needs to be global for all inventory ops.
* Added a base inventory connector that does common processing of inventory among all reference connector implementations. E.g. AddItem requires additional processing before being forwarded to service.
* Added if (m_Enabled) upon RemoveRegion
|
|
|
|
|
|
| |
upon client close.
Commented remote call on GetSystemFolders again, so that it's not live yet.
|
| |
|
|
|
|
| |
sizes. * Now, what's available of the terrain will show and it'll be truncated if it's larger on Linden Clients. Parcel minimum is 64 (256/4) for the client to accept it.
|
|
|
|
| |
lets you configure region sizes to be smaller without crashing the region. I remind you that regions are still square, must be a multiple of 4, and the Linden client doesn't like anything other then 256. If you set it bigger or smaller, the terrain doesn't load in the client, the map has issues, and god forbid you connect it to a grid that expects 256m regions.
|
|
|
|
| |
256m limitation within the OpenSimulator framework, however, the LLClient ClientView does not support regions larger then 256 meters so, if you try and make your region larger by setting Constants.RegionSize = 512; in OpenSim.Framework.Constants.cs, the terrain will not display on clients using the LLUDP protocol
|
|
|
|
|
| |
Moved the Close() for the appdomain-hosted parts into a new destructor
on ScriptInstance.
|
|\ |
|
| |
| |
| |
| | |
use this abstraction.
|
|/
|
|
|
| |
This matches behavior seen with an earlier attempt to do this, apparently
the sponsor mechanism does't work in Mono
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
|Date: Wed, 5 Aug 2009 09:51:52 -0700
|Subject: [PATCH] Closed two major memory leaks for scripted objects
|
|Two major memory leaks for the scripted objects were fixed
|- One leak had to do with remoting acrossing app domains. When a script and
| its controlling agent communicate across an application boundary, it calls
| functions on a stub proxy object that then invokes the remote method on
| the object in the other app domain. These stub objects (two for each script)
| were setup to have infinate lifetimes and were never being garbage collected.
|- The second leak was the result of adding a scene object part instance method
| to a scene event and never removing it. This cause the event's delegate list
| to maintain a link to that object which is then never freed as the scene event
| object is never destroyed.
Patch applied, please direct feedback to me. Possible issue: Longtime idle
scripts like vendors may fail.
|
| |
|
|
|
|
| |
Signed-off-by: dr scofield (aka dirk husemann) <drscofield@xyzzyxyzzy.net>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
[1] Added a new OnAttach event to Scene/EventManager
[2] Hooked up existing attach event handler in XEngine.
[3] Modified SceneGraph and Scene.Inventory to trigger
attach events at the appropriate places. I was forced
to distribut the changes across two files because of
the way attach processing is distributed across the
two files.
[4] In the case of RezSingleAttachmentFromInventory it is
necessary to handle event scheduling in a special way.
There is no synchronous path available, so the fact
that this object is attached, and who it is attached to,
is cached when the ScriptInstance is created. When
the script is started, the attached handler is driven
after on_rez (but before changed, this should be reviewed).
Signed-off-by: dr scofield (aka dirk husemann) <drscofield@xyzzyxyzzy.net>
|
|
|
|
| |
allow final deletion of objects. Meant to support the attach(NULL_KEY) event,
|
| |
|
|
|
|
|
|
| |
Fixes Mantis #3946
|
|
|
|
|
|
|
|
| |
* Uses mantis #3811 as a base (thanks jhuliman) with changes.
* E-mail regarding interface changes sent to the opensim-dev list
* Archive: https://lists.berlios.de/pipermail/opensim-dev/2009-July/007219.html
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
module interface. This fixes an issue where region references were being added but weren't being deleted,
causing those "unnotified circuit" messages.
* Also fixes tests accordingly
- Fixes Mantis #3452
- Fixes Mantis #3388
- Fixes Mantis #3871
- Related to Mantis #3493
|
|
|
|
|
|
| |
* Commented logic that wasn't being used.
* This should fix the errors in OdeScene.near
|