On 14 Feb 2012, at 21:21, Milan Mimica wrote: > On 14 February 2012 21:09, Sven Van Caekenberghe <s...@beta9.be> wrote: > > There was a semaphore related problem in 1.3 that was fixed some time ago. > Doing regular image saves was one of the factors involved. > Search the mailing list or issues list for semaphore. > > Nah, leaking one semaphore per image save is not a problem. I don't save > regularly. The remark on image saving was that when you save the image, you > save all the crap that is running, and it accumulates every time. There is no > point saving an image in production if you are persisting data externally. > Besides that I don't remember anything related being fixed.
These are not necessarily related, but these are some of them: http://code.google.com/p/pharo/issues/detail?id=4910 http://code.google.com/p/pharo/issues/detail?id=4768 http://code.google.com/p/pharo/issues/detail?id=4505