One of the nagging problems we have appears to be memory leaks. There are
consistent and frustrating reports of more heavily used regions using up all
the RAM, then starting swap, then lagging, then freezing every week.
In order to help bring a little clarity to this, Nebadon has put together:
One could catch the objects which are causing the leak by using a
profiler. If someone has .NET profiler and skills he could try to
trace the source of the problem so it can be fixed...
-Tommi
___
Opensim-dev mailing list
Opensim-dev@lists.berlios.de
It's really the proliferation of eternal caches that causes issues,
IMHO.
Melanie
Tommi Laukkanen wrote:
One could catch the objects which are causing the leak by using a
profiler. If someone has .NET profiler and skills he could try to
trace the source of the problem so it can be fixed...
Ouch I forgot that evil madness. It would be good to put in proper
caches which drop items based on time. Eternal caches are well..
antipattern. Namely intentionally build memory leak. Anti patterns are
well known arch demons of software design and we should try to purge
them off the code base ,)
+1
Patches welcome.
Melanie
Tommi Laukkanen wrote:
Ouch I forgot that evil madness. It would be good to put in proper
caches which drop items based on time. Eternal caches are well..
antipattern. Namely intentionally build memory leak. Anti patterns are
well known arch demons of software
