Hi, For the GC problem from https://github.com/OpenSmalltalk/opensmalltalk-vm/issues/391, there is no threading involved. Just invoking full GC in a large image.
Cheers, Doru > On Nov 11, 2019, at 1:47 PM, ducasse <steph...@netcourrier.com> wrote: > > Hi doru > > > Can you tell us more? How many threads are running? how many times did you > save the image? > Pablo is investigating a bug related to the GC that happens when we have many > threads and saved the image > multiple times. He was on it since a couple of days. > > Now Pablo is attending Smalltalks and will be on vacation until end of the > month. > Guille is on father leave and coming back to work one day a week. > > So we are concerned about this problem but we cannot really allocate people > on it before beginning of december. > > S. > >> On 11 Nov 2019, at 12:57, Tudor Girba <tu...@tudorgirba.com> wrote: >> >> Hi, >> >> During our work we encountered two issues we think should be considered >> critical. >> >> The first is that the garbage collector is unreliable on larger images: >> https://github.com/OpenSmalltalk/opensmalltalk-vm/issues/391 >> We stumble on this when we manipulate larger pieces of data quite >> consistently in plain Pharo (7 or 8). We lack the knowledge of how to >> approach it, but we would happily pair and try to reproduce it with someone. >> >> The second one is that the sources contain wrong pointers, and this makes it >> hard to work with TFFI: >> https://github.com/pharo-project/pharo/issues/4967 >> This is already marked as important. We spent quite some time investigating >> this, especially in the context of TFFI, and we would be happy to pair to >> work through it. >> >> Would anyone be available for a collaboration in the following days? >> >> Cheers, >> Doru >> >> >> -- >> feenk.com >> >> "Not knowing how to do something is not an argument for how it cannot be >> done." >> >> > > > -- feenk.com "Value is always contextual."
