Crash report: https://crash-stats.mozilla.org/report/index/d4cd0ea6-a7fb-4d3e-9fa8-f94110230511

Reason: SIGSEGV / SEGV_MAPERR

Top 10 frames of crashing thread:

0  libxul.so  mozilla::dom::AnimationTimeline::Tick  dom/animation/AnimationTimeline.cpp
1  libxul.so  mozilla::dom::DocumentTimeline::MostRecentRefreshTimeUpdated  dom/animation/DocumentTimeline.cpp:178
2  libxul.so  nsRefreshDriver::Tick  layout/base/nsRefreshDriver.cpp:2567
3  libxul.so  mozilla::RefreshDriverTimer::TickDriver  layout/base/nsRefreshDriver.cpp:373
3  libxul.so  mozilla::RefreshDriverTimer::TickRefreshDrivers  layout/base/nsRefreshDriver.cpp:351
4  libxul.so  mozilla::VsyncRefreshDriverTimer::RunRefreshDrivers  layout/base/nsRefreshDriver.cpp:911
4  libxul.so  mozilla::VsyncRefreshDriverTimer::TickRefreshDriver  layout/base/nsRefreshDriver.cpp:825
5  libxul.so  mozilla::VsyncRefreshDriverTimer::NotifyVsyncOnMainThread  layout/base/nsRefreshDriver.cpp:746
6  libxul.so  mozilla::VsyncRefreshDriverTimer::RefreshDriverVsyncObserver::NotifyVsyncTimerOnMainThread  layout/base/nsRefreshDriver.cpp:592
7  libxul.so  mozilla::VsyncRefreshDriverTimer::RefreshDriverVsyncObserver::NotifyVsync  layout/base/nsRefreshDriver.cpp:549

This looks like a mostly-Android crash which spiked back in February.

I mark this S3 for now because the number of crashes is not a lot in fx117. Let's monitor this bug for more versions.