Updates:
Status: FixReviewNeeded
Comment #3 on issue 6375 by
[hidden email]: OCompletion uses a lot
of memory
http://code.google.com/p/pharo/issues/detail?id=6375The attached slice
-> adds a reset method to NOCompletionTable
-> remove all the prefil methods (to load selectors from .changes or
kernel/collections)
Reason: they have been evaluated months ago and the data is out of
sync
evaluating them on startup is too slow
-> add NOCompletionTable to ShutDownList. do a reset
What this means is that now NOCompletion just learns the classes you are
using in one session.
Data is cleared on shutdown.
Name: SLICE-Issue-6375-OCompletion-uses-a-lot-of-memory-MarcusDenker.1
Author: MarcusDenker
Time: 14 November 2012, 1:43:40.978 pm
UUID: 3986d006-561d-4ea7-879e-45d0ea4b73e5
Ancestors:
Dependencies: NOCompletion-MarcusDenker.28
Issue 6375: OCompletion uses a lot of memory
_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker