Logging out and back in also solves the issue for me. I guess that a dll
handle is not released properly.
Phil
On Wed, Dec 12, 2018, 16:14 Guillermo Polito
>
> On Sun, Dec 9, 2018 at 2:26 AM Ben Coman wrote:
>
>> Just reporting a strange occurrence in case anyone sees the same.
>>
>> I was usin
On Wed, 12 Dec 2018 at 23:14, Guillermo Polito
wrote:
>
>
> On Sun, Dec 9, 2018 at 2:26 AM Ben Coman wrote:
>
>> Just reporting a strange occurrence in case anyone sees the same.
>>
>> I was using PharoLauncher fine, then it wasn't.
>> When trying to launch an image it started reporting with "Pr
On Sun, Dec 9, 2018 at 2:26 AM Ben Coman wrote:
> Just reporting a strange occurrence in case anyone sees the same.
>
> I was using PharoLauncher fine, then it wasn't.
> When trying to launch an image it started reporting with "ProcessWrapper
> newProcess failed..."
>
Has your Pharo launcher bee
Just reporting a strange occurrence in case anyone sees the same.
I was using PharoLauncher fine, then it wasn't.
When trying to launch an image it started reporting with "ProcessWrapper
newProcess failed..."
First time I've ever seen that, and fixed by a reboot, but still strange.
There are a co
