Bug 224151 – ASSERTION FAILED: unifiedTextCheckerEnabled() when searching for "mdn text" on google.com

• Status: NEW
• Component: HTML Editing

[Tyler Wilcock]

Steps to reproduce the crash:

0. `Tools/Scripts/build-webkit --debug` (2019 MBP, macOS 10.15.7)
1. `Tools/scripts/run-minibrowser --debug`
2. Go to google.com via the address bar
3. Type "mdn text" into the search box and press enter.

ASSERTION FAILED: unifiedTextCheckerEnabled()
./editing/Editor.cpp(2694) : void WebCore::Editor::markAllMisspellingsAndBadGrammarInRanges(OptionSet<WebCore::TextCheckingType>, const Optional<WebCore::SimpleRange> &, const Optional<WebCore::SimpleRange> &, const Optional<WebCore::SimpleRange> &)
1   0x47fdeb0a9 WTFCrash
2   0x4608fa24b WTFCrashWithInfo(int, char const*, char const*, int)
3   0x463b97f10 WebCore::Editor::markAllMisspellingsAndBadGrammarInRanges(WTF::OptionSet<WebCore::TextCheckingType>, WTF::Optional<WebCore::SimpleRange> const&, WTF::Optional<WebCore::SimpleRange> const&, WTF::Optional<WebCore::SimpleRange> const&)
4   0x463b2e2a1 WebCore::AlternativeTextController::timerFired()
5   0x463b542d7 decltype(*(std::__1::forward<WebCore::AlternativeTextController*&>(fp0)).*fp()) std::__1::__invoke<void (WebCore::AlternativeTextController::*&)(), WebCore::AlternativeTextController*&, void>(void (WebCore::AlternativeTextController::*&)(), WebCore::AlternativeTextController*&)
6   0x463b54250 std::__1::__bind_return<void (WebCore::AlternativeTextController::*)(), std::__1::tuple<WebCore::AlternativeTextController*>, std::__1::tuple<>, __is_valid_bind_return<void (WebCore::AlternativeTextController::*)(), std::__1::tuple<WebCore::AlternativeTextController*>, std::__1::tuple<> >::value>::type std::__1::__apply_functor<void (WebCore::AlternativeTextController::*)(), std::__1::tuple<WebCore::AlternativeTextController*>, 0ul, std::__1::tuple<> >(void (WebCore::AlternativeTextController::*&)(), std::__1::tuple<WebCore::AlternativeTextController*>&, std::__1::__tuple_indices<0ul>, std::__1::tuple<>&&)
7   0x463b54209 std::__1::__bind_return<void (WebCore::AlternativeTextController::*)(), std::__1::tuple<WebCore::AlternativeTextController*>, std::__1::tuple<>, __is_valid_bind_return<void (WebCore::AlternativeTextController::*)(), std::__1::tuple<WebCore::AlternativeTextController*>, std::__1::tuple<> >::value>::type std::__1::__bind<void (WebCore::AlternativeTextController::*&)(), WebCore::AlternativeTextController*>::operator()<>()
8   0x463b5418e WTF::Detail::CallableWrapper<std::__1::__bind<void (WebCore::AlternativeTextController::*&)(), WebCore::AlternativeTextController*>, void>::call()
9   0x46090eac2 WTF::Function<void ()>::operator()() const
10  0x46094b1de WebCore::Timer::fired()
11  0x4649f49f4 WebCore::ThreadTimers::sharedTimerFiredInternal()
12  0x4649ff151 WebCore::ThreadTimers::setSharedTimer(WebCore::SharedTimer*)::$_0::operator()() const
13  0x4649ff0de WTF::Detail::CallableWrapper<WebCore::ThreadTimers::setSharedTimer(WebCore::SharedTimer*)::$_0, void>::call()
14  0x46090eac2 WTF::Function<void ()>::operator()() const
15  0x4649ab45b WebCore::MainThreadSharedTimer::fired()
16  0x464a7b556 WebCore::timerFired(__CFRunLoopTimer*, void*)
17  0x7fff30b0b7f9 __CFRUNLOOP_IS_CALLING_OUT_TO_A_TIMER_CALLBACK_FUNCTION__
18  0x7fff30b0b35f __CFRunLoopDoTimer
19  0x7fff30b0ae47 __CFRunLoopDoTimers
20  0x7fff30aefbea __CFRunLoopRun
21  0x7fff30aeee3e CFRunLoopRunSpecific
22  0x7fff3318a1d8 -[NSRunLoop(NSRunLoop) runMode:beforeDate:]
23  0x7fff3323cc7f -[NSRunLoop(NSRunLoop) run]
24  0x7fff6add54ea _xpc_objc_main.cold.4
25  0x7fff6add5430 _xpc_objc_main
26  0x7fff6add4f63 _xpc_copy_xpcservice_dictionary
27  0x450d511c8 WebKit::XPCServiceMain(int, char const**)
28  0x4523d452b WKXPCServiceMain
29  0x10c8b4ea2 main
30  0x7fff6ab87cc9 start
2021-04-03 11:10:41.728 MiniBrowser[25543:4294912] WebContent process crashed; reloading

[Radar WebKit Bug Importer]

<rdar://problem/76359781>

[Alexey Proskuryakov]

Chris, have you fixed this in bug 258356?

[Chris Dumez]

(In reply to Alexey Proskuryakov from comment #2)
> Chris, have you fixed this in bug 258356?

Seems likely but we should verify.