On 18 Jun 2013, at 10:38, Camillo Bruni <[email protected]> wrote:
> the original issue you posted was closed because it is a duplicate of this one > https://pharo.fogbugz.com/default.asp?7526 I saw that, but the title is too restrictive I think. > where you will fine a proper script to kill hanging processes… OK, but it is not good to keep on producing images with all this shit in them. Maybe we need some QA type unit test that checks for unexpected processes. > On 2013-06-18, at 10:05, Sven Van Caekenberghe <[email protected]> wrote: >> On 18 Jun 2013, at 09:47, Camille Teruel <[email protected]> wrote: >> >>> >>> On 18 juin 2013, at 09:32, Sven Van Caekenberghe wrote: >>> >>>> Hi, >>>> >>>> It seems that >>>> https://pharo.fogbugz.com/f/cases/10760/Lots-and-Lots-of-Delay-wait-processes-die-to-Cookie-contents >>>> is closed, but the problem remains. >>>> >>>> Yesterday I test deployed a brand new 3.0 image. It has more than 800 >>>> bogus delay related processes. >>>> >>>> … >>>> >>>> <Screen Shot 2013-06-18 at 09.30.30.png> >>>> >>>> This is not good ;-) >>>> >>>> The least we should do is add some script in the release/build process to >>>> kill them. >>> >>> I added the following to my startup preferences: >>> >>> Process allInstances do: [ :process | >>> process suspendedContext ifNotNil: [ :context | >>> context method = (Delay>>#wait) ifTrue: [ process terminate ] ] >>> ] >> >> OK, thanks. >> But are we sure that no legitimate ones are killed ? >> I am not sure, but I believe Igor's script had more tests…. >> >>>> >>>> Sven >>>> >>>> >>>> -- >>>> Sven Van Caekenberghe >>>> Proudly supporting Pharo >>>> http://pharo.org >>>> http://association.pharo.org >>>> http://consortium.pharo.org >>>> >>>> >>>> >>>> >>> >> >> > >
