Posted: Fri Jan 20, 2006 2:40 pm
Slow day at work as the boss just got me the file he should've given me two days ago & I don't feel like diving into a new project only to have half the brain cells that remembered it dead on Tuesday from booze.
Anyhoo, checked the forums for info on the memory leak. There are some prevalent themes :
(1) Both the server & client are written in Stackless Python.
(2) Upgrading to .NET 2.0 has helped some, made no difference to others, and magnified the problem for the remainder. This seems very odd as memory leaks are due to incompetent clearing of memory or faulty garbage collection. Python shouldn't be affected by anything in .NET.
(3) Some just didn't've any leaks whatsoever at all, nor've they ever'd any.
Some dude mentioned something called cacheman that he uses to manage his memory & he said he didn't've any leaks.
Where're the devs to weigh in on this shit? Is it the client, the server, or what?
Anyhoo, checked the forums for info on the memory leak. There are some prevalent themes :
(1) Both the server & client are written in Stackless Python.
(2) Upgrading to .NET 2.0 has helped some, made no difference to others, and magnified the problem for the remainder. This seems very odd as memory leaks are due to incompetent clearing of memory or faulty garbage collection. Python shouldn't be affected by anything in .NET.
(3) Some just didn't've any leaks whatsoever at all, nor've they ever'd any.
Some dude mentioned something called cacheman that he uses to manage his memory & he said he didn't've any leaks.
Where're the devs to weigh in on this shit? Is it the client, the server, or what?