Pharo Issue Tracker - Manuscript (Case [Issue]22770) Crosscutting and Misc - MetacelloProjectRegistration is significantly leaking

Manuscript Notification

	Pavel Krivanek opened Case 22770: MetacelloProjectRegistration is significantly leaking and assigned it to Everyone: Bug in Crosscutting and Misc: 1. Pharo Image • You are subscribed to this case

The MetacelloProjectRegistration is used to identify versions of loaded baselines/configurations. But the real object graph of its register holds literally everything - the living instances of configurations, Monticello definitions etc.

We probably should not touch it in Pharo 7 but it deserves fixing because it may significantly increase image size. I have seen an image that contained 60 MB in this registry.

The MetaceloSpec instances keep their loader.
MetacelloMCVersion instances keep loaderPolicy.

<code>
MetacelloSpec allSubInstances do: [ :e | e instVarNamed: #loader put: nil].
MetacelloMCVersion allInstances do: [ :e | e loaderPolicy: nil ].
nil
</code>

	Priority: 2 – Really Important		Status: Work Needed
	Assigned to: Everyone		Milestone: Pharo8.0

Go to Case

No longer need updates? Unsubscribe from this case.

Don't want Manuscript notifications anymore? Update your preferences.

_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
https://lists.gforge.inria.fr/mailman/listinfo/pharo-bugtracker