[Pharo-dev] two issues: GC and wrong pointers
tudor at tudorgirba.com
Tue Nov 12 02:58:47 EST 2019
Yes, I know it’s not a good public bug report. That is why I asked for help.
The problem is that this is not easily reproducible outside of specific cases. We encountered it in the context of GT which has double the code as compared to Pharo. So, to test it outside of GT, for the last couple of weeks we manipulated some data in plain Pharo, and we still got to the problem a couple of times (though it appears less often). We do not know yet how to reproduce it with anonymous data. That is why I said that some pairing might help.
In parallel we are trying to reproduce it, like we do with all other bug reports.
> On Nov 12, 2019, at 8:00 AM, ducasse <stepharo at netcourrier.com> wrote:
>> On 11 Nov 2019, at 12:57, Tudor Girba <tudor at tudorgirba.com> wrote:
>> 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:
>> 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.
> To me this is not really a good bug report.
> How can we reproduce it?
> What is a big image?
> The first thing to do is to get a simple reproducible case.
> This is what pavel did with the crash on normal images.
> Can you see if you can do something like that?
> It will help us trying to fix it.
"What is more important: To be happy, or to make happy?"
More information about the Pharo-dev