On 20 February 2012 16:47, Milan Mimica <milan.mimica@gmail.com> wrote:
On 14 February 2012 23:54, Milan Mimica <milan.mimica@gmail.com> wrote:
On 14 February 2012 22:55, Igor Stasenko <siguctua@gmail.com> wrote:
semaphores collect: [:sema | Â Â Â Â sema -> Â Â Â Â Â Â Â Â (sema pointersTo reject: [:ptr | ptr == arr or: [ptr == semaphores ] ] ) ]
Can you try invoking it on your image , look for those who has an empty array, which will mean that there is no references to it except semaphore table itself.
There is 69 of such semaphores, out of hundreds in total. Not much :-/ On a normal image there is only a few.
Should say that the 69 leaked semaphores are probably there because of the bug that leaks a semaphore on each image save. Still, that should be causing major problems in my case.
Well, that should not cause problem unless you keep the image running and running and running (so garbage accumulates). And of course, if you restart an image, an external semaphore table wiped out.. so i think we having a side effect of running image stably for quite a long duration (and this is positive part) , but which uncovering such bags :)
-- Milan Mimica http://sparklet.sf.net
-- Best regards, Igor Stasenko.