It seems to be fixed in Pharo5 already. Debugger comes up within less than a
second and is usable.
Marcus
> On 29 Aug 2015, at 11:57, H. Hirzel <[email protected]> wrote:
>
> Andrei,
>
> Thanks for confirming the bug.
>
> Report is here
>
>
> https://pharo.fogbugz.com/f/cases/16425/Pharo-4-0-Inspecting-a-recursive-data-structure-is-slow
>
> --Hannes
>
> On 8/29/15, Andrei Chis <[email protected]> wrote:
>> Hi Hannes,
>>
>> Can open a bug report?
>> I though most recursive problems were fixed in the new inspector.
>> Seems that there are still some related to printing recursive structures.
>>
>> You can switch to the previous inspector (GTInspector
>> setGTInspectorEnabledStatus: false),
>> however, this bug seem to also kill that inspector.
>>
>> Cheers,
>> Andrei
>>
>> On Sat, Aug 29, 2015 at 7:16 AM, H. Hirzel <[email protected]> wrote:
>>
>>> Hello
>>>
>>> I have realized that inspecting a recursive data structure is very
>>> slow in Pharo 4.0
>>>
>>> A test case:
>>>
>>> | myDict |
>>> myDict := Dictionary new.
>>> myDict at: #hello put: 'hello'.
>>> myDict at: #recurHello put: myDict.
>>> myDict inspect
>>>
>>> It takes a long time for the inspector to come up. And the image
>>> freezes later on if you continue.
>>>
>>> The problem is with the inspector because if I do
>>> | myDict |
>>> myDict := Dictionary new.
>>> myDict at: #hello put: 'hello'.
>>> myDict at: #recurHello put: myDict.
>>> 3 + 4 inspect
>>>
>>> it comes up instantly.
>>>
>>>
>>> As a comparison I attach the Cuis ** test result. The inspector comes
>>> up instantly and the image does not have any problems.
>>>
>>>
>>> What are the workarounds in Pharo 4.0?
>>>
>>> - Setting a time out somewhere?
>>> - Disabling certain functions?
>>> - Loading a simpler inspector?
>>>
>>> Regards
>>>
>>> Hannes
>>>
>>>
>>> ** current build 2463.image
>>> https://github.com/Cuis-Smalltalk/Cuis-Smalltalk-Dev
>>>
>>
>
