On Sat, Mar 5, 2016 at 1:59 AM, Nicolai Hess <nicolaih...@gmail.com> wrote:
>
>
> 2016-03-04 17:15 GMT+01:00 Ben Coman <b...@openinworld.com>:
>>
>> Hi Peter, I see you had this problem 12 months ago.
>>
>> http://lists.pharo.org/pipermail/pharo-users_lists.pharo.org/2015-February/017026.html
>>
>> What you can try is in development mode, closing the PharoLauncher
>> window, nil out class variables and garbage collect, then check what
>> instances remain of PharoLauncher classes.
>>
>> cheers -ben
>
>
>
> I use pharo launcer a lot (on windows) and I did not see any slow down.
> But I don't use it for anything else then launching the images.
> Do you notice the slow down by launching images or do you use the
> PharoLauncher image for anything else?

I think it was more when I was helping with PharoLauncher development
and would close down/open it a lot.  Since I've been mostly only using
it I haven't noticed the problem.  Or the root of that particular
issue was fixed.
cheers -ben



>
>>
>>
>> On Fri, Mar 4, 2016 at 6:42 PM, Peter Uhnák <i.uh...@gmail.com> wrote:
>> > Yeah I saw that when he was in Prague (incidentally that's where my
>> > launcher
>> > slowdown started :)).
>> >
>> > I've removed write access and will report back in couple of days. :)
>> >
>> > Thanks,
>> > Peter
>> >
>> > On Fri, Mar 4, 2016 at 11:24 AM, Damien Cassou <damien.cas...@inria.fr>
>> > wrote:
>> >>
>> >> Hi Peter,
>> >>
>> >> Peter Uhnák <i.uh...@gmail.com> writes:
>> >> > I've been using Pharo Launcher for quite a while and problem that I
>> >> > am
>> >> > constantly encountering is that launching of it becomes slower and
>> >> > slower.
>> >>
>> >> Stéphane, in CC, reported the same months ago on OS X. I don't know if
>> >> Stéphane still experiences the problem. Could you please try to remove
>> >> write access to the .image and .changes files?
>> >>
>> >> --
>> >> Damien Cassou
>> >> http://damiencassou.seasidehosting.st
>> >>
>> >> "Success is the ability to go from one failure to another without
>> >> losing enthusiasm." --Winston Churchill
>> >
>> >
>>
>

Reply via email to