On 24.08.2017 18:04, Erich Steinböck wrote:
> This issue doesn't show up on Windows or Linux. I can't test on Mac.
>
> Can anyone of you running ooRexx on Mac confirm it? Does it happen for you
> too?
Just ran it (the five invocations saying the pid followed by the grep for rexx
processes) on my
MacOSX using my own builds of the trunk code (which is right of the official
Cmake definitions) and
it does not happen here (no leftover processes)!
As to the revision number of my ooRexx 5.0beta version, I do not know (neither
"rexx -v" nor "parse
versrion v" do not tell), but it was created from the trunk as of August 11, so
is farely new.
Maybe Marc is using an older version of ooRexx or not from the official Cmake
definitions?
> We don't have too many fork()'s in our Code - for this issue probably only
> those in APIService and
> SysLocalAPIManager might be relevant. Would anyone be willing to add printf's
> after each fork,
> giving the returned pid, and build and run it. Rony, maybe?
If needed I can try to do this and report back, but would probably only be able
to do so sometimes
over the weekend, if still necessary.
---rony
---------- Forwarded message ----------
> From: *Marc Simpson* <mar...@users.sf.net <mailto:mar...@users.sf.net>>
> Date: Thu, Aug 24, 2017 at 4:48 PM
> Subject: [oorexx:bugs] Re: #1475 ooRexx (r11290) doesn't exit cleanly on macOS
> To: "[oorexx:bugs]" <1...@bugs.oorexx.p.re.sf.net
> <mailto:1...@bugs.oorexx.p.re.sf.net>>
>
>
> In answer to your questions:
>
> * `oorexx` is a symlink to `rexx` in the installation target.
> * Yes, the process seems to linger indefinitely.
> * Yes, processes accumulate over time. (I first spotted the problem when I
> had 50+ sleeping
> processes, all associated with the same script.)
>
> Finally, here's the result of your test, run a few times:
>
> ~~~
> $ for i in {1..5}; do oorexx -e "say SysQueryProcess('pid')"; done
> 31022
> 31024
> 31026
> 31028
> 31030
> $ ps ax | grep rexx | grep -v grep
> 31023 ?? Ss 0:00.00 oorexx -e say SysQueryProcess('pid')
> 31025 ?? Ss 0:00.00 oorexx -e say SysQueryProcess('pid')
> 31027 ?? Ss 0:00.00 oorexx -e say SysQueryProcess('pid')
> 31029 ?? Ss 0:00.00 oorexx -e say SysQueryProcess('pid')
> 31031 ?? Ss 0:00.00 oorexx -e say SysQueryProcess('pid')
> ~~~
>
> (Note that I killed 16195 just before running this.)
>
>
> ---
>
> ** [bugs:#1475] ooRexx (r11290) doesn't exit cleanly on macOS**
>
> **Status:** open
> **Group:** 5.0.0
> **Created:** Wed Aug 23, 2017 11:01 PM UTC by Marc Simpson
> **Last Updated:** Thu Aug 24, 2017 08:57 AM UTC
> **Owner:** nobody
>
>
> ooRexx doesn't exit cleanly on macOS, leaving behind a sleeping process:
>
> ~~~
> $ ps ax | grep oorexx | grep -v grep
> $ oorexx -e 'say 123'
> 123
> $ ps ax | grep oorexx | grep -v grep
> 16195 ?? Ss 0:00.00 oorexx -e say 123
> $ oorexx -v
> Open Object Rexx Version 5.0.0
> Build date: Aug 23 2017
> Addressing mode: 64
> [...]
> ~~~
>
> N.B. I'm unable to reproduce the problem on Linux.
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel
