Hi Norman,
If you're closing a View window while the process execute some REBOL code, the window will be destoyed but the process will remain in memory until it finish executing the code. In your case, by setting v-frames to a high value, you create a very long loop that will stay alive even after you've closed the window. So i guess you've hit the [x] button +/- 7 times to obtain the windowless processes...(Sending a "Ctrl-C" signal to the process will make it terminate cleanly) You can see more clearly the issue if you add a 'print "showing console..." line at the beginning of the %vball.r script. Then run your test and you will see that the console is still there after you close the window. BTW, the VBall apps could avoid such issue by calling a 'quit in a window 'close event handler. HTH, -DocKimbel. PS: 2.5.2 looks like more a /Core version...;-) Rebolinth wrote: > > Hello All, > > When using the VBALLS demo with /view and I change: > > v-frames: choice 50x20 "100" "200" "400" "1000" "2000" font-size 10 > into -> > v-frames: choice 50x20 "100" "200" "400" "1000" "900000" font-size 10 > > and select "900000" as frames option when starting. > > Then Vballs produces background processes under windows. > After running vballs for 8 hours it has created +/- 7 forked > processes (dead???).. > > Using Windows /View.. 2.5.2 > > Anyone any idea why that happens? > > (R)egards, > Norman. -- To unsubscribe from this list, please send an email to [EMAIL PROTECTED] with "unsubscribe" in the subject, without the quotes.
