[Glass] orphaned classes do not disappear

Dale Henrichs via Glass glass at lists.gemtalksystems.com
Fri Mar 17 11:48:55 PDT 2017

Ah, very interesting ... I think that in 3.3.3 we just might have been 
able to find those references .... IIRC:) ... I know that we have 
focused in this area for both 3.3.3 and 3.4 to try to improve things  
... I've got a work in progress project called Object explorer[1] where 
I'm building some tools for finding references and tracking down object 
paths ... the project is aimed at 3.4, because we've added some new 
support for finding parents of objects (efficiently) and this provides a 
way to pretty much guarantee that you can find the references that are 
keeping an object alive ... The object explorer is an interactive tool 
... finding all reference paths automatically without getting someone 
with domain knowledge involved  can be difficult because recursive data 
structures cause big time memory/performance issues ...


[1] https://github.com/dalehenrich/obex

On 03/17/2017 11:09 AM, Johan Brichau via Glass wrote:
> Dale,
> I discovered I had GsBackupScan64 loaded in this extent and there is a 
> class variable ‘Classes’ that keeps a mapping oop -> class.
> Needless to say… I cannot even remember I loaded it into this extent 
> :) This was probably done in the very early days of Yesplan.
> Too bad those references did not show up when scanning the references.
> I’m down to just a very short list of classes now. So I’m guessing I 
> will be out of the woods soon on this one.
> Johan
>> On 17 Mar 2017, at 17:10, Johan Brichau <johan at yesplan.be 
>> <mailto:johan at yesplan.be>> wrote:
>> Hi Dale,
>>> On 16 Mar 2017, at 23:14, Dale Henrichs via Glass 
>>> <glass at lists.gemtalksystems.com 
>>> <mailto:glass at lists.gemtalksystems.com>> wrote:
>>> Is the object that you are searching for holding onto a lot other 
>>> state or otherwise preventing you from upgrading? If it is just an 
>>> annoyance?
>> As there are no instances of these classes anymore, it’s an 
>> annoyance, as I’m wondering what is referencing these classes.
>> I just did a bit more poking and when I emptied the method 
>> dictionaries for these classes, many of them were garbage collected.
>> It’s not just our own classes, but I also see a lot of Metacello* and 
>> XML* class(-versions) in that list.
>> I will probably just try what you suggested and see what info I get 
>> in 3.3.3
>>> If you consider it a real problem and you are willing to share a 
>>> copy of your db, we'd be willing to try to figure out what's going 
>>> on --- in our case, we'd more than likely upgrade the db ourselves 
>>> and debug the issue there ... if it is still an issue:)
>> Thx, if I’m still lost in a week from now, I might just send in a 
>> ticket for help :)
>> Johan
> _______________________________________________
> Glass mailing list
> Glass at lists.gemtalksystems.com
> http://lists.gemtalksystems.com/mailman/listinfo/glass

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.gemtalksystems.com/mailman/private/glass/attachments/20170317/4c8f6c83/attachment-0001.html>

More information about the Glass mailing list