Bugzilla

I can't absolutely rule any weird side effects, but I'm still fairly certain that bug 1494748 doesn't do anything that's fundamentally different from how Android normally saves a view's state.

I'm probably not really qualified to speculate much further, but poking around on crash-stats for other crashes involving nsIFrame::GetOffsetToCrossDoc brings up a number of other crashes that (assuming the stack isn't bogus) also have the LiveSavedFrameCache on the stack. So bug 1516514 (https://hg.mozilla.org/releases/mozilla-beta/rev/666a44dfa6eb) could be another suspect here?

I can't absolutely rule any weird side effects, but I'm still fairly certain that bug 1494748 doesn't do anything that's fundamentally different from how Android normally saves a view's state.

I'm probably not really qualified to speculate much further, but [poking around on crash-stats](https://crash-stats.mozilla.com/search/?proto_signature=~GetOffsetToCrossDoc&proto_signature=~LiveSavedFrameCache&product=FennecAndroid&date=%3E%3D2018-10-21T11%3A40%3A59.000Z&date=%3C2019-01-21T10%3A40%3A59.000Z&_sort=-date&_facets=signature&_columns=date&_columns=signature&_columns=product&_columns=version&_columns=build_id&_columns=platform#facet-signature) for other crashes involving nsIFrame::GetOffsetToCrossDoc brings up a number of other crashes that (assuming the stack isn't bogus) also have the LiveSavedFrameCache on the stack. So bug 1516514 (https://hg.mozilla.org/releases/mozilla-beta/rev/666a44dfa6eb) could be another suspect here?