| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |\ |
|
| | |
| |
| |
| | |
CreateNotecardAsset()
|
| | | |
|
| |\ \
| |/ |
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| | |
location rather than copying.
Copying doesn't prevent IOExceptions on Windows due to file locking. (e.g. Mantis 5642, 5630).
So instead go back to moving the file, swallowing IOExceptions that occur just for the move due to competing caching threads or even different opensimulator instances.
|
| | |
| |
| |
| |
| |
| |
| |
| |
| | |
the memory cache even when it wasn't enabled.
This hopefully addresses http://opensimulator.org/mantis/view.php?id=5634
This is the most probable cause of the memory problems that people have been seeing in the past month.
This bug has been around since commit 5dc785b (4th July 2011). Doh! This is why regressions tests are such a good idea... :)
Many thanks to Nebadon for using git bisect to track down this bug, which made it a 5 minute fix.
|
| | | |
|
| | | |
|
| | | |
|
| | |
| |
| |
| |
| |
| | |
disk, copy it instead.
This is to eliminate IOException where two threads compete to cache the same file.
|
| | | |
|
| | |
| |
| |
| | |
specific stuff to return more information.
|
| | |
| |
| |
| | |
this command is invoked.
|
| |\ \
| |/ |
|
| | | |
|
| | | |
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| |
| | |
This matches the ability to disable the memory part
This is controlled through the FileCacheEnabled parameter in FlotsamCache.ini
Default is true, so existing installations are not affected.
Improved fcache command feedback when various caches are disabled.
Re-enabled test for flotsam cache with file caching disabled.
|
| | |
| |
| |
| | |
already been done for the memory cache
|
| | |
| |
| |
| | |
Disabled temporarily since file system caching disrupts subsequent test runs
|
| |\ \
| |/ |
|
| | |
| |
| |
| | |
its own, clear both memory and file caches
|
| | |
| |
| |
| |
| |
| |
| |
| |
| | |
config-include/FlotsamCache.ini.example. Enable the flotsam console commands even if FlotsamCache.ini isn't present.
For the most part, defaults are made to match those already in FlotsamCache.ini.example.
The one exception is that the 48 hour file timeout from the code is used instead of the 0 hours that was in the example file. This can be tweaked if necessary.
Most importantly, the default cache directory is now ./assetcache (as in FlotsamCache.ini.example) rather than ./FlotsamAssetCache (as was the internal code default).
Therefore, if you were using flotasm without using the config file, then please rename your cache directory or start using the ini file and change the default there if you want to keep using your existing cache.
|
| |\ \
| |/ |
|
| | |
| |
| |
| | |
CACHE] section is missing or just the particular config values
|
| | |
| |
| |
| |
| |
| | |
there is a [FLOTSAM ASSET CACHE] section present at all, use the same default all the time
this simplifies the code
|
| | |
| |
| |
| | |
the default
|
| | |
| |
| |
| |
| |
| | |
asset cache to try using Double.MaxValue, which would cause the underlying OpenMetaverse.ExpiringCache to choke.
There is probably an underlying bug to fix in ExpiringCache.
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| | |
cache only
* Adds GetTextureModule that implements the "GetTexture" capability, aka HTTP texture fetching. This is a significantly optimized path that does not require any server-side JPEG2000 decoding, texture priority queue, or UDP file transfer
* Sanity check for null reference in LLClientView.RefreshGroupMembership()
|
| | | |
|
| | | |
|
| |\ \
| |/
|/| |
|
| | | |
|
| |/
|
|
|
|
| |
types are inferred from context
* OAR saving will attempt to correct unknown asset types before writing broken assets to the OAR file
|
| |
|
|
| |
bin/config-include/FlotsamCache.ini.example
|
| | |
|
| |
|
|
|
|
|
| |
This resolves the problem where eyes and hair would turn white on standalone configurations
When a client receives body part information, for some insane reason or other it always ends up uploading this back to the server and then immediately re-requesting it.
This should have been okay since we stored that asset in cache. However, the standalone asset service connector was not checking this cache properly, so every time the client made the request for the asset it has just loaded it would get a big fat null back in the face, causing it to make clothes and hair white.
This bug did not affect grids since they use a different service connector.
|
| |
|
|
|
|
|
|
| |
config-include/StandaloneCommon.ini [Modules] (or no [Modules] at all)"
This will be replaced by a better solution where an enabled baking module will fail if no cache is in place (same for dynamic texture modules)
This reverts commit 7058a4c2597a2b76704e906b73ae7077ff805b16.
|
| |
|
|
|
|
|
| |
config-include/StandaloneCommon.ini [Modules] (or no [Modules] at all)
If this is the case, this patch makes CenomeAssetCache the default cache (which matches that selected in StandaloneCommon.ini.example)
Not having an asset cache may lead to a continual loop of appearance baking failures and cause dynamic textures not to work, among other effects
|
| |
|
|
|
| |
Fix command params check on fcache expire <datetime>
Thanks coyled
|
| | |
|
| |
|
|
|
|
| |
Util.FireAndForget()
* Changed Util.FireAndForget() to use any of five different methods set with async_call_method in the [Startup] section of OpenSim.ini. Look at the example config for possible values
|
| |
|
|
|
|
| |
and UDP code
* Changing the cache modules to only initialize the caches if they are actually enabled. Should save a bit of resources from unused cache systems
|
| |
|
|
| |
* Replaced calls to ThreadPool.QueueUserWorkItem() with ThreadPool.UnsafeQueueUserWorkItem() since OpenSim does not use Code Access Security sandboxing
|
| | |
|
| |
|
|
| |
Thank you, mcortez.
|
| | |
|
| | |
|
