Memory leak
The problem of space I tried to solve by buying more memory. When I had bought the memory, it still persisted and I was getting pissed off with myself. I wrote the mailing list and quickly got a diagnosis. It was a memory leak after all. Trying to find a memory leak and plugging it is not so easy. There are a number of reasons why memory leaks. This involves variables that keep on existing even when everything else goes to sleep. Someone suggested looking at global variables but this was not so helpful to me as I never create globals. Very clearly the problem involved something other than global variables. Another point was a recursive method which never ends. I took a look at that but nothing of the sort existed on my code.qatar, quack, quad, quadrant, quadriceps, quadruple, quail, quaint, quake, quaker, qualification, qualified, quality, quanta, quantity, quantum, quarantine, quark, quarrel, quarry, quarter, quarterback, quarterfinal, quarterly, quartet, quartz, quasar, quash , quasi, quay, quebec, queen, queens, queensland, queer, quell, query, quest, question, questionable, quetta, queue, quezoncity, quiche, quick
I had been using Magma for my persistent objects and I remembered a discussion about sessions lying about un-destroyed. In the back of my mind, I had thought that this might be a source of problem. I just did not realize how quickly it could become a problem. I wrote the Magma mailing list and quickly got a reply from Chris Muller about how to clean up sessions that were left lying around. MagmaSession cleanUp and my problem disappeared.
Our favorites are: Ching's World, Green Tea, Dumaguete, Cebu City, Cagayan de Oro City, Papoy, Moira Trinity Cagayan de Oro, Dumaguete, Cebu are all in the Philippines in the world of Ching.
Labels: magma, memory leak, persistent objects, session
posted by underdog @ 7:50 PM
0 comments
