Crash report: https://crash-stats.mozilla.org/report/index/b371c15a-e5ce-49ab-aabe-c40870210823

Reason: EXC_BAD_ACCESS / KERN_INVALID_ADDRESS

Top 10 frames of crashing thread:

0 XUL mozilla::a11y::HyperTextAccessibleWrap::LengthForRange accessible/mac/HyperTextAccessibleWrap.mm:334
1 XUL mozilla::a11y::GeckoTextMarkerRange::Length const accessible/mac/GeckoTextMarker.mm:545
2 XUL -[MOXTextMarkerDelegate selectionChangeInfo] accessible/mac/MOXTextMarkerDelegate.mm:143
3 XUL -[mozAccessible handleAccessibleEvent:] accessible/mac/mozAccessible.mm:1028
4 XUL -[mozTextAccessible handleAccessibleEvent:] accessible/mac/mozTextAccessible.mm:325
5 XUL mozilla::a11y::AccessibleWrap::HandleAccEvent accessible/mac/AccessibleWrap.mm:235
6 XUL nsEventShell::FireEvent accessible/base/nsEventShell.cpp:44
7 XUL mozilla::a11y::SelectionManager::ProcessTextSelChangeEvent accessible/base/SelectionManager.cpp:154
8 XUL mozilla::a11y::EventQueue::ProcessEventQueue accessible/base/EventQueue.cpp:329
9 XUL mozilla::a11y::NotificationController::WillRefresh accessible/base/NotificationController.cpp:889

Seems like a null pointer crash

Comment on the crash report is "Running the Babbel web app cursor behaves strangely. Then it crashed! Works OK in Google Chrome."

Since the crash volume is low (less than 5 per week), the severity is downgraded to S3. Feel free to change it back if you think the bug is still critical.

For more information, please visit auto_nag documentation.