There is nothing protecting the range object.
This used to not be a problem before this patch because temporary objects in C++ are deleted after the full expression is evaluated, so it wasn't destroyed until after the function call.
Created attachment 88702 [details]
Comment on attachment 88702 [details]
View in context: https://bugs.webkit.org/attachment.cgi?id=88702&action=review
> + Now that the Range is used outide the full expression where it's created, it needs to be