2017-04-03 15:00 GMT+02:00 Esteban Lorenzano <[email protected]>: > Hello, > > This are the things I believe still needs to be solved to be able to > release Pharo 6.0: > > VM: > === > - win32, cairo fonts problem (I submitted a new VM to test, I think this > is fixed :P) > - make all tests pass (there are still some failing tests when compiling a > new VM)/. > - libgit2: Still not there, Jan and Ben were trying and sent some > suggestions but I still didn’t had the time to test it. > > Image: > ===== > > - iceberg still needs to go inside the image, I’m running to release > version 0.4 (maybe this week?) and then we can integrate. > - I'm still convinced there is a leak. I need to check this in detail. And > of course some help on this… Pavel?… would be cool :) >
I have found one memory leak related to subscription type mixing: https://pharo.fogbugz.com/f/cases/19911 Then I had here a really huge image with 1.2 GB with all known memory leaks solved. It was leaking because of Undeclared, after cleaning of them (Undeclared removeUnreferencedKeys) it shrinked to 59 MB. In this particular case it was caused by code like this: initialize super initialize. noBindingBlock := [ objectSpace nilObject ] because noBindingBlock was undeclared, it created a reference from globals (Undeclared) to a particular context with all mess it referenced. Not sure if we should make some action like clean Undeclared before every snapshot. But the case like this is quite obscure and the information that people should beware it should be enough. Cheers, -- Pavel > List is a lot smaller now :) > If everything goes well, we can target to release next week. > > Next: > - Test the new process and tape some videos explaining how we will > contribute with a bootstrapped process using github :) > > cheers! > Esteban >
