Crashes with Apple's SpeechSynthesis framework's BabelFish class on stack
Categories
(Core :: Web Speech, defect)
Tracking
()
People
(Reporter: smichaud, Unassigned, NeedInfo)
Details
Crash Data
Attachments
(1 file)
|
3.42 KB,
text/rtf
|
Details |
These are almost entirely on macOS 14, on Intel Macs, and have increased dramatically with the most recent release -- 14.5. They're presumably an Apple bug.
Their signature, unfortunately, is shared with many other unrelated bugs. Here's how to search for this bug's crashes:
Typical crash stack:
Crashing Thread (110), Name: SpeechWorker
Frame Module Signature Source Trust
0 XUL CrashReporter::TerminateHandler() toolkit/crashreporter/nsExceptionHandler.cpp:1880 context
1 libc++abi.dylib std::__terminate(void (*)()) cfi
2 libc++abi.dylib std::terminate() cfi
3 libobjc.A.dylib objc_terminate cfi
4 libdispatch.dylib _dispatch_client_callout cfi
5 libdispatch.dylib _dispatch_lane_barrier_sync_invoke_and_complete cfi
6 SpeechSynthesis -[BabelFish allVoices] cfi
7 SpeechSynthesis BFCountVoices(short*) cfi
8 AppKit +[NSSpeechSynthesizer availableVoices] cfi
9 XUL mozilla::dom::EnumVoicesRunnable::Run() dom/media/webspeech/synth/cocoa/OSXSpeechSynthesizerService.mm:282 cfi
10 XUL nsThread::ProcessNextEvent(bool, bool*) xpcom/threads/nsThread.cpp:1193 inlined
10 XUL NS_ProcessNextEvent(nsIThread*, bool) xpcom/threads/nsThreadUtils.cpp:480 cfi
11 XUL mozilla::ipc::MessagePumpForNonMainThreads::Run(base::MessagePump::Delegate*) ipc/glue/MessagePump.cpp:300 cfi
12 XUL MessageLoop::RunInternal() ipc/chromium/src/base/message_loop.cc:370 inlined
12 XUL MessageLoop::RunHandler() ipc/chromium/src/base/message_loop.cc:363 inlined
12 XUL MessageLoop::Run() ipc/chromium/src/base/message_loop.cc:345 cfi
13 XUL nsThread::ThreadFunc(void*) xpcom/threads/nsThread.cpp:370 cfi
14 libnss3.dylib _pt_root nsprpub/pr/src/pthreads/ptthread.c:201 cfi
15 libsystem_pthread.dylib _pthread_start cfi
16 libsystem_pthread.dylib thread_start cfi
|
Reporter | |
Comment 1•2 years ago
|
||
Someone from Mozilla should probably report this bug to Apple.
|
||
Comment 2•2 years ago
|
||
The bug is linked to a topcrash signature, which matches the following criterion:
- Top 5 desktop browser crashes on Mac on release
For more information, please visit BugBot documentation.
|
|
Reporter | |
Comment 3•2 years ago
•
|
||
For what it's worth, I've found a way to exercise the code that crashes, but not to make it crash:
https://web-api-examples.github.io/speech.html
In this example, add some text under "Demo - Text to Speech", then click "Tap to Speak".
|
||
Comment 4•2 years ago
|
||
(In reply to Steven Michaud [:smichaud] (Retired) from comment #1)
Someone from Mozilla should probably report this bug to Apple.
Thanks, Steven. I'll get this filed with Apple.
|
|
||
Comment 5•2 years ago
|
||
I've filed FB13814516 and have alerted our Apple contact.
|
|
Reporter | |
Comment 6•2 years ago
|
||
These crashes still happen on macOS 14.6 and up, but their numbers are much reduced. Tentatively, I'm going to call this bug fixed.
|
|
Reporter | |
Updated•2 years ago
|
|
|
Reporter | |
Updated•2 years ago
|
|
|
Reporter | |
Comment 7•2 years ago
|
||
But there are still a lot of these crashes on macOS 14.6 and up -- 117 over the last week. So I'm going to reopen this again :-(
|
|
Reporter | |
Updated•2 years ago
|
|
|
Reporter | |
Comment 8•1 year ago
|
||
For what it's worth, this bug also effects Safari, and there's a workaround:
|
|
Reporter | |
Comment 9•1 year ago
|
||
I'm not sure why, but this bug's crashes seem to have been "fixed" (worked around) by the latest patch for bug 1880582.
Here's how to search for this bug's crashes on builds that have that patch. There aren't any, even after several days of 133.0b releases.
|
|
Reporter | |
Updated•1 year ago
|
|
||
Updated•1 year ago
|
|
|
Reporter | |
Comment 10•1 year ago
|
||
(In reply to Steven Michaud [:smichaud] (Retired) from comment #9)
I'm not sure why, but this bug's crashes seem to have been "fixed" (worked around) by the latest patch for bug 1880582.
Here's how to search for this bug's crashes on builds that have that patch. There aren't any, even after several days of 133.0b releases.
But now there are some crashes with the latest patch for bug 1880582. So this bug isn't fixed.
bp-4a1920ba-e5d4-4105-aa01-739e20241105
bp-873ebcf6-5184-4eb6-9693-e075b0241105
bp-3be8b9b5-3711-49e7-b7ff-731930241105
|
|
Reporter | |
Updated•1 year ago
|
|
|
||
Updated•1 year ago
|
|
||
Comment 11•1 year ago
|
||
I'm not actively working on this. Taking myself off the Bug.
|
|
||
Updated•1 year ago
|
|
|
||
Comment 12•1 year ago
|
||
Based on the topcrash criteria, the crash signatures linked to this bug are not in the topcrash signatures anymore.
For more information, please visit BugBot documentation.
|
|
||
Comment 13•1 month ago
|
||
The severity field is not set for this bug.
:padenot, could you have a look please?
For more information, please visit BugBot documentation.
|
||
Comment 14•1 month ago
|
||
Eitan, can you check this one?
Description
•