Smalltalk › Pharo › Pharo Smalltalk Developers

Pharo 5: browser windows are extremely resource hungry

_‹ Previous Topic Next Topic _›

Classic

List

Threaded

5 messages Options

Max Leske

Pharo 5: browser windows are extremely resource hungry

Hi

I discovered that in Pharo 5, having two or more browser windows open significantly reduces responsiveness in the image (delayed clicks, ghosting when moving windows etc.). This is especially true if a method has been selected in two or more windows. The ghosting becomes much worse when you drag a window. I checked that the same does not happen in Pharo 4.

I originally thought that there was a strong impact on CPU load too, but it’s actually not that bad.

Has anybody seen this or even worked on a fix for it? If not, I’ll open a bug report.

Cheers,
Max

Max Leske

Re: Pharo 5: browser windows are extremely resource hungry

Apparently this is a polling bug in the new FastTable. FastTable should not have been activated yet Esteban told me and in the newest build indeed FastTable has been deactivated again and the behaviour I described is no longer reproducible.

Max

> Hi
>
> I discovered that in Pharo 5, having two or more browser windows open significantly reduces responsiveness in the image (delayed clicks, ghosting when moving windows etc.). This is especially true if a method has been selected in two or more windows. The ghosting becomes much worse when you drag a window. I checked that the same does not happen in Pharo 4.
>
> I originally thought that there was a strong impact on CPU load too, but it’s actually not that bad.
>
> Has anybody seen this or even worked on a fix for it? If not, I’ll open a bug report.
>
>
> Cheers,
> Max

EstebanLM

Re: Pharo 5: browser windows are extremely resource hungry

> On 16 Jul 2015, at 09:10, Max Leske <[hidden email]> wrote:
>
> Apparently this is a polling bug in the new FastTable. FastTable should not have been activated yet Esteban told me and in the newest build indeed FastTable has been deactivated again and the behaviour I described is no longer reproducible.

this :)

Esteban

>
> Max
>
>> Hi
>>
>> I discovered that in Pharo 5, having two or more browser windows open significantly reduces responsiveness in the image (delayed clicks, ghosting when moving windows etc.). This is especially true if a method has been selected in two or more windows. The ghosting becomes much worse when you drag a window. I checked that the same does not happen in Pharo 4.
>>
>> I originally thought that there was a strong impact on CPU load too, but it’s actually not that bad.
>>
>> Has anybody seen this or even worked on a fix for it? If not, I’ll open a bug report.
>>
>>
>> Cheers,
>> Max
>

Henrik Sperre Johansen

Re: Pharo 5: browser windows are extremely resource hungry

> On 16 Jul 2015, at 9:36 , Esteban Lorenzano <[hidden email]> wrote:
>
>
>> On 16 Jul 2015, at 09:10, Max Leske <[hidden email]> wrote:
>>
>> Apparently this is a polling bug in the new FastTable. FastTable should not have been activated yet Esteban told me and in the newest build indeed FastTable has been deactivated again and the behaviour I described is no longer reproducible.
>
> this :)
>
> Esteban
>
>>
>> Max
>>
>>> Hi
>>>
>>> I discovered that in Pharo 5, having two or more browser windows open significantly reduces responsiveness in the image (delayed clicks, ghosting when moving windows etc.). This is especially true if a method has been selected in two or more windows. The ghosting becomes much worse when you drag a window. I checked that the same does not happen in Pharo 4.
>>>
>>> I originally thought that there was a strong impact on CPU load too, but it’s actually not that bad.
>>>
>>> Has anybody seen this or even worked on a fix for it? If not, I’ll open a bug report.
>>>
>>>
>>> Cheers,
>>> Max
>>
>
>

Should've named it FastTableExceptWhenSlow until it's out of beta ;)

Cheers,
Henry

Sean P. DeNigris

Re: Pharo 5: browser windows are extremely resource hungry

Administrator

Henrik Sperre Johansen wrote

Should've named it FastTableExceptWhenSlow until it's out of beta ;)

Ha ha ha. Actually, I was thinking that it's pretty cool that Pharo treats even alpha versions with care, immediately rolling back changes which break core things.

Cheers,
Sean