21 Jul
2021
21 Jul
'21
9:12 a.m.
The problem always happens during weak storage scan. Inflation of a lock creates new weak handle that points back to the object. I suspect that, at the very least, this must not point to the old copy of that object. I need to think this through.
Is the lock inflation provoked by the GC thread itself, as a side effect of reading the klass?
Yes. The more I think about it, the more I come to the conclusion that this might be a no-go, except maybe for a dirty prototype (which is my current goal, tbh). Can you share more about Robbin's work? Because this sounds like it would help avoid such problems. Thanks, Roman