#1258 working set grows when call syssleep in loop

[Igor]

when i run this code working set grows. if i comment line --call syssleep 0.5 does not grow

Q_=.RexxQueue~new('TO_GEARBOX')
Q_~empty
QUIK_FILE='C:\2QUIK'
i=1
loop
if .file~new(QUIK_FILE)~length=0 then do
L=Q_~pull
call syssleep 0.5
end
end

[Rick McGuire]

Really going to need more here. First of all, what interpreter version and system are you running on.

Secondly, how are you determining that the working set is growing. On Windows at least, I'm not seeing any growth in working set size. The only difference the syssleep calls appear to make is how quickly the working set reaches a steady state.

[Igor]

Windows 7 (64) SP1, rexx 4.2.0.9940, procexp.exe shows that working set grows.
1.jpg & 2.jpg screenshots of procexp.exe

thanks

---

On Tue, 4/15/14, Rick McGuire bigrixx@users.sf.net wrote:

Subject: [oorexx:bugs] #1258 working set grows when call syssleep in loop
To: "[oorexx:bugs]" 1258@bugs.oorexx.p.re.sf.net
Date: Tuesday, April 15, 2014, 10:03 PM

Really going to
need more here. First of all, what interpreter version and
system are you running on.

Secondly, how are you determining that the working set is
growing. On Windows at least, I'm not seeing any growth
in working set size. The only difference the syssleep calls
appear to make is how quickly the working set reaches a
steady state.

[bugs:#1258]
working set grows when call syssleep in loop
Status: open

Group: 4.1.2

Created: Tue Apr 15, 2014 06:51 PM UTC by
Igor

Last Updated: Tue Apr 15, 2014 06:51 PM
UTC

Owner: nobody
when i run this code working set grows. if i comment line
--call syssleep 0.5 does not grow
Q_=.RexxQueue~new('TO_GEARBOX')

Q_~empty

QUIK_FILE='C:\2QUIK'

i=1

loop

if .file~new(QUIK_FILE)~length=0 then do

   L=Q_~pull

   call syssleep 0.5

end

end

Sent from sourceforge.net because you indicated interest
in https://sourceforge.net/p/oorexx/bugs/1258/
To unsubscribe from further messages, please visit https://sourceforge.net/auth/subscriptions/

[Igor]

working set 8820K (1.jpg) then 12788K (2.jpg). also it can see standard windows task manager (ctrl+alt+del). i tested it in 2 different PC workins set grows.

---

On Wed, 4/16/14, Rick McGuire bigrixx@users.sf.net wrote:

Subject: [oorexx:bugs] #1258 working set grows when call syssleep in loop
To: "[oorexx:bugs]" 1258@bugs.oorexx.p.re.sf.net
Date: Wednesday, April 16, 2014, 1:59 PM

status:
open --> invalidGroup: 4.1.2
--> NoneComment:
I and seeing absolutely no difference in working set size
between these programs nor any evidence of a memory leak,
even after over 12 hours of running time.

[bugs:#1258]
working set grows when call syssleep in loop
Status: invalid

Group: None

Created: Tue Apr 15, 2014 06:51 PM UTC by
Igor

Last Updated: Tue Apr 15, 2014 07:03 PM
UTC

Owner: nobody
when i run this code working set grows. if i comment line
--call syssleep 0.5 does not grow
Q_=.RexxQueue~new('TO_GEARBOX')

Q_~empty

QUIK_FILE='C:\2QUIK'

i=1

loop

if .file~new(QUIK_FILE)~length=0 then do

   L=Q_~pull

   call syssleep 0.5

end

end

Sent from sourceforge.net because you indicated interest
in https://sourceforge.net/p/oorexx/bugs/1258/
To unsubscribe from further messages, please visit https://sourceforge.net/auth/subscriptions/

[Rick McGuire]

I and seeing absolutely no difference in working set size between these programs nor any evidence of a memory leak, even after over 12 hours of running time.

[Anonymous]

working set 8820K (1.jpg) then 12788K (2.jpg). also it can see standard windwos task manager (ctrl+alt+del). i tested it in 2 different PC.

[Rick McGuire]

ooRexx uses a garbage collecting storage management mechanism. The only difference the sysSleep call appears to make is it slows the time it takes for the first garbage collection event to kick in, which can manifest as a growth in working set. Both versions of the program stabilize at the same storage usage once the first garbage collection occurs. There is no bug here.