Baseline loading initialize a TKT process that keeps the whole stack alive

[VincentBlondeau]

In BaselineOfLargeImageSupport>>postload:package: , the indexes are generated and creates a TKTWorker that at some point becomes at WatchDog process:

This WatchDog keeps a copy to the worker orignal stack. The copied stack goes to the method that loaded the baseline and beyond. This creates a memory leak where objects linked to those contexts should have been GC'ed.

Here is the full stack that is copied in the WatchDog process:
largeImageLoading.txt