get_next_shape_internal: Skip VM lock for single child caseHEADmaster

If the shape has only one child, we check it lock-free without compromising thread safety. I haven't computed hard data as to how often that it the case, but we can assume that it's not too rare for shapes to have a single child that is often requested, typically when freezing and object. 

0 files changed, 0 insertions, 0 deletions