| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
|
|
| |
actually a little more work than I expected given the copious
use of out params.
|
|
|
|
|
|
| |
to reflect what they really are.
|
|
|
|
| |
what just went wrong
|
|
|
|
|
|
|
|
| |
* wrap attributes in properties
* clean up names a little bit
* clean up name styles
|
|
|
|
|
|
|
|
| |
* wrap fields as Properties
* rename some fields/properties to more sensible names
* set style to PropName to match more standard C# approach
|
|
|
|
|
|
| |
Patch to remove commented NotImpemented calls from within implemented script functions
|
|
|
|
| |
to one
|
|
|
|
|
|
|
|
|
|
|
|
| |
affect once the region and the grid servers have upgraded to this revision
* You may also need to clear your cache before seeing any effect.
* These fixes may or may not affect inventory on the RC client.
* These fixes should make non-root folders work better, stop inventory failure on first login, allow trash to be emptied and make texture picker in object edit view work properly
* Fixes are 1) make initial root folder request wait for async inventory delivery, 2) deliver all folders in the initial login skeleton, not just the root child ones and 3) deal
with situations where we receive child folders from the inventory service before their parent is received.
|
|
|
|
|
|
|
|
|
| |
than just the root child folders
* This may resolve some current problems with non root child folders on standalone installations.
* A fix for the same problem in grid mode will come soon.
|
| |
|
| |
|
|
|
|
|
|
|
| |
now show up.
Most likely still some problems and most like needs some more work (and still a couple of things to finish off).
|
|
|
|
|
|
| |
* Reduce 'asset not found' console debug spam
|
| |
|
|
|
|
| |
asset cache, until it can be seen if the module was the cause of some new problems that seem like they might be related to assets. I'll look into this more tomorrow.
|
|
|
|
| |
functions are no longer in AssetCache
|
|
|
|
|
|
|
|
| |
ever seen". I'm not sure I should be doing this commit, but oh well.
So anyway, it moves the Asset downloading (packet sending) to a module (AssetDownloadModule).
So now at last, AssetCache should be just dealing with fetching assets from the asset server and caching them.
|
| |
|
|
|
|
| |
happening due to locks in the AssetCache and Texturedownload module. Where the thread from the Asset thread would be take a lock on a list in the asset cache and then try to call the Callback into the texturedownload module and hit a lock in there which was held by a ClientView thread- which at the same time would be trying to request another texture from the cache and be hitting the lock in there held by the IClientAPI. The result each thread waiting for the other one to release a lock. And as one of those was the ClientView process packet thread. No more packets from that client could be processed. For now I've made a copy of the list in AssetCache so that it can release the lock. I'm doing more work on assets (moving the client asset downloading to a module ), so will hopefully change this into a better method once I've cleaned over things up a bit.
|
|
|
|
|
|
|
|
|
|
|
|
| |
an image
* This might stop some client's constant requests for unfound textures, which is a candidate for the memory leak
* If a texture is not found then the "Image not found" texture will now be displayed clientside
* If it works, this should resolve mantis 676
* Non texture image requests do not receive this packet yet
* This will require a prebuild
|
|
|
|
|
|
|
| |
* Correct asset cache stats table heading
* Correct spelling mistake in AssetCache (thanks ChrisD!)
|
|
|
|
|
|
|
| |
* As such, only a request for a non cached asset, the response and failures show up now.
* I know lbsa71 only put these in not long ago, so if they are really still required, I think we should think whether we can move the default log4net level off 'Debug'
|
|
|
|
| |
compiled in DEBUG mode)... Its ugly and even requires a separate thread to track the treads, but it will be very valuable in debugging.
|
|
|
|
|
|
|
| |
* Resolve a bad logic bug in AssetCache.GetAsset()
* This may make some asset related things work better (possibly getting main map images will now be improved).
|
|
|
|
|
|
|
|
|
| |
data from the asset server
* This should stop the constant increase in the download requests statistics
* If you see stat numbers for download requests which are far from what you'd expect, please report
|
|
|
|
| |
(my own bug)
|
|
|
|
|
|
| |
* Add documentation to AssetCache
|
| |
|
| |
|
|
|
|
|
|
|
| |
* This fixes some of the 'runaway downloads' problem but not all of it
* Also fix up logging messages so texture requests are reported as such rather than as assets
|
|
|
|
|
|
| |
* turned script asset fetching asynchronous
|
|
|
|
|
|
|
|
| |
scene)
* Fixed ClickAction situation on the same note (properties shouldn't cause big changes)
* Added some more debug output to AssetCache
|
|
|
|
| |
threads so it will be easier to debug.
|
|
|
|
|
|
|
| |
CommsManager and into a module (AgentAgentTransactionModule), still needs cleaning up though.
But its one more thing out of the CommsManager. One day we will kill the CommsManager!
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
* This may or may not help with the memory leak, need to assess
|
|
|
|
|
|
|
|
| |
* Push asset update (invoked when clothing is altered) down into AgentAssetTransactions from Scene.Inventory.cs to join others
* I've tested that clothing creation and update still works, but please let me know if it suddently breaks for you.
* Add/correct comments
|
| |
|
|
|
|
|
|
| |
* Should resolve mantis 542
|
|
|
|
|
|
|
|
|
| |
align classes with file names
* Small amount of ndoc
* This will probably require a prebuild and nant clean
|
| |
|
| |
|
| |
|
|
|
|
| |
think first transfer of asset should start faster.
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
'show assets' shows the current state of the asset cache (number of cached assets, requests, et c)
'clear-assets' forcibly re-initializes the asset cache thereby freeing all cached items.
'clear-assets' is not to be used lightly, as it probably introduces mem inconsistencies and doubling up of textures.
|