Issue 3529 in pharo: TextMorph>>releaseCachedState creates a paragraph which causes a "Subscript out of bounds" in an internal RunArray

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

Issue 3529 in pharo: TextMorph>>releaseCachedState creates a paragraph which causes a "Subscript out of bounds" in an internal RunArray

pharo
Status: Accepted
Owner: [hidden email]
Labels: Type-ReportDefect

New issue 3529 by [hidden email]: TextMorph>>releaseCachedState  
creates a paragraph which causes a "Subscript out of bounds" in an internal  
RunArray
http://code.google.com/p/pharo/issues/detail?id=3529

Pharo image: Pharo1.1rc3
Pharo core version: Latest update: #11406
Virtual machine used: Pharo 4.0.2

Steps to reproduce:
1. ScriptLoader new cleanUpForRelease.

or

2. Specifically

SystemNavigation default
        allObjectsDo: [ :each |
                (each respondsTo: #releaseCachedState)
                        ifTrue: [ each releaseCachedState ] ].

Sometimes creating a new paragraph while releasing caches causes an Error  
(subscript is out of bounds) in the RunArray of the text attributes of the  
TextComposer in the MultiNewParagraph which is contained. Attached Error  
log.
The method TextMorph>>paragraph says "Paragraph instantiation is lazy -- it  
will be created only when needed", then why the (undocumented)  
TextMorph>>releaseCachedState creates a new paragraph anyway? If creating  
paragraph is not needed you may apply the proposed fix.



Attachments:
        releaseParagraphBug.log  29.9 KB
        TextMorph-releaseCachedState.st  234 bytes


Reply | Threaded
Open this post in threaded view
|

Re: Issue 3529 in pharo: TextMorph>>releaseCachedState creates a paragraph which causes a "Subscript out of bounds" in an internal RunArray

pharo
Updates:
        Status: FixProposed

Comment #1 on issue 3529 by [hidden email]:  
TextMorph>>releaseCachedState creates a paragraph which causes a "Subscript  
out of bounds" in an internal RunArray
http://code.google.com/p/pharo/issues/detail?id=3529

(No comment was entered for this change.)