Re: [Pharo-dev] why so many processes are running at startup time?

June 20, 2013

      Caekenberghe san

11 lines of code in previous e-mail, extracted from SmalltalkImage>>
privCleanProcesses (20607 image), and modified.

Browser fullOnClass: SmalltalkImage selector: #privCleanProcesses.
or
Nautilus fullOnClass: SmalltalkImage selector: #privCleanProcesses.

please use freely.

regards.

2013/6/21 Sven Van Caekenberghe <sven@stfx.eu>
...
Hi Satoshi,
On 20 Jun 2013, at 12:18, NISHIHARA Satoshi <goonsh@gmail.com> wrote:
...
thx.
I run a cleaning processes script such as:
      (Process allInstances
              reject: [ :p |
                      {(InputEventFetcher default fetcherProcess).
                      (Processor activeProcess).
                      (WeakArray runningFinalizationProcess).
                      (Processor backgroundProcess).
                      (SmalltalkImage current lowSpaceWatcherProcess).
                      (UIManager default uiProcess).
                      (Delay schedulingProcess)} includes: p ])
              do: [ :p |
                      p suspend; terminate ]
This code looks like a nice start for writing a unit test that could
verify that there are no bogus processes in delivered images.
We already have a number of tests that do global quality checks (like
Undeclared, bogus instances, ..), we need this as well.
Any opinions, comments ?
Sven
...
and get 6 processes remain:
(80)  745275392: Delay class>>handleTimerEvent
(60) Input events fetching process: InputEventFetcher>>waitForInput
(60) 1061945344: SmalltalkImage>>lowSpaceWatcher
(50)  946339840: WeakArray class>>finalizationProcess
(40s) Morphic UI process: nil
(10)  845938688: ProcessorScheduler class>>idleProcess
is this OK?
regards.
2013/6/20 Marcus Denker <marcus.denker@inria.fr>
Hi,
I think we should for now just kill them when building the image, I will
check.
On Jun 20, 2013, at 9:56 AM, ClÃ©ment Bera <bera.clement@gmail.com>
wrote:
...
Hello,
These processes are due to the new integration testing process. This
new process was introduced in Pharo 3.0 alpha, and we found the bug and
fixed it.
Recently we backport the new integration process to Pharo 2.0 and
seemingly it created the same bug but since we read your mail we were not
aware of it. We need to backport the fix.
We will fix that within a few days.
As a workaround, you can just kill these processes in your image for
now ...
Thanks for reporting the issue,
2013/6/20 NISHIHARA Satoshi <goonsh@gmail.com>
There are 30 over processes are running at startup, Pharo-20607.image.
<NDOWS-1252?B?vIgyMDEzLTA2LTIwIDEzLjE5LjU277yJLnBuZw=.png>
regards.
--
--
"NISHIHARA Satoshi"
[:goonsh :nsh | ^ nishis perform: goonsh with: nsh]
--
ClÃ©ment BÃ©ra
Mate Virtual Machine Engineer
BÃ¢timent B 40, avenue Halley 59650 Villeneuve d'Ascq
--
--
"NISHIHARA Satoshi"
[:goonsh :nsh | ^ nishis perform: goonsh with: nsh]
-- 
--
"NISHIHARA Satoshi"
[:goonsh :nsh | ^ nishis perform: goonsh with: nsh]