On Wed, May 18, 2016 at 6:46 PM, Paul DeBruicker <pdebruic@gmail.com> wrote:
the reason I asked about OSProcess in Pharo 5 was that
OSProcess waitForCommand: 'ls'
never returned.
Maybe its another instance of this problem. And it happens everytime.
There is a 50ms delay in the #waitForCommand: method
It looks quite similar indeed. And... both, OSProcess and OSSubprocess have a similar child watcher (I based mine in OSProcess one). Paul could you inspect the child process from the process browser tool, do an inspect, and check the suspended process? Check the wait time to see if it is 50ms or 20ms etc...that way we can see which part is the "hunging".
hope this helps
Paul
Mariano Martinez Peck wrote
On Wed, May 18, 2016 at 2:10 PM, Ben Coman <
btc@
> wrote:
I don't have time to look at this properly until tomorrow. In the meantime, could you just post the result of...
Delay delaySchedulerClass it should be "DelayExperimentalSpinScheduler" ***
Yes, it is.
Also could you try a few of the other options from World > System > Settings > System ...
Do you know which is the "Safest" to use? Or at least which was used in say, 4.0?
***whoops, the Experimental tag should have been dropped for Pharo 5 Release. Its been fine for months (unless this is a fault :) ]
Yes, I found that strange too.
Maybe it is wrong to keep and re-use same instance of Delay? (note it
is
outside the closure) (this was not a problem in the past).
Not sure. I've heard others say Delays should only be used once. To experiment, could you try creating a delay each time.
Ok, I will try this. But again, it would take some some time to test and it happens to me every in while only.
Thanks!!
-- Mariano http://marianopeck.wordpress.com
-- View this message in context: http://forum.world.st/Problem-with-delay-waiting-OSSubprocess-code-on-Pharo-... Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.
-- Mariano http://marianopeck.wordpress.com