Product Firefox Release Channel release Version 92.0 Build ID 20210903235534 (2021-09-03) Buildhub data OS OS X 10.15 OS Version 10.15.7 19H1323

https://support.mozilla.org/en-US/kb/update-firefox-latest-version?cache=no Did you update Firefox to the latest version?

Version 92.0.1, first offered to Release channel users on September 23, 2021

Tue, 21 Sep 2021 22:14:03 GMT bp-058c91cd-4b9c-46d1-bd12-640ba0210928 Signature: PLDHashTable::Search | mozilla::a11y::AccAttributes::GetAttribute

Crash Reason EXC_BAD_ACCESS / KERN_INVALID_ADDRESS

This is for Sumo's Related Bugs 1717501 NEW --- Crash in [@ PLDHashTable::Search | mozilla::a11y::AccAttributes::GetAttribute]

The report you posted is a week old. Do you have any newer crashes?

Start Firefox using Troubleshoot(Safe) Mode {web link}

A small dialog should appear. Click Start In Troubleshoot(Safe) Mode (not Refresh). Is the problem still there?

Thank you for your reply.

I already tried troubleshoot mode several times. I'm on the latest version of FF, I just checked. I maybe wasn't for a few of the recent crashes I've had, but I know for a fact that I've already had crashes on the newest version.

here are some more crash report ID's, I have more if needed:

• bp-c4db3a84-355b-4da6-a78f-9dd2d0210928
• bp-0c10ba61-bd6c-448d-843b-235140210928
• bp-85e7f180-de33-42c1-b85a-2ad670210928

I called for more help.

Product Firefox Release Channel release Version 92.0 Build ID 20210903235534 (2021-09-03)

Sun, 12 Sep 2021 23:11:22 GMT bp-c4db3a84-355b-4da6-a78f-9dd2d0210928 Mon, 13 Sep 2021 01:11:07 GMT bp-0c10ba61-bd6c-448d-843b-235140210928

Signature: PLDHashTable::Search | mozilla::a11y::AccAttributes::GetAttribute

Crash Reason EXC_BAD_ACCESS / KERN_INVALID_ADDRESS

This is for Sumo's Related Bugs 1717501 NEW --- Crash in [@ PLDHashTable::Search | mozilla::a11y::AccAttributes::GetAttribute] +++++++++++++++++++++++++++++++++++++++++++ Product Firefox Release Channel release Version 92.0.1 Build ID 20210922161155 (2021-09-22)

Mon, 27 Sep 2021 22:21:58 GMT bp-85e7f180-de33-42c1-b85a-2ad670210928 Signature: PLDHashTable::Search | mozilla::a11y::AccAttributes::GetAttribute

Crash Reason EXC_BAD_ACCESS / KERN_INVALID_ADDRESS

This is for Sumo's Related Bugs 1717501 NEW --- Crash in [@ PLDHashTable::Search | mozilla::a11y::AccAttributes::GetAttribute]

Ok thank you very much Fred.

You can try to disable accessibility services in Firefox (look at the bottom of the article).

• https://support.mozilla.org/en-US/kb/accessibility-services

Thank you but I already tried disabling accessibility services and it didn't work.

The crashes are accessibility (a11y) related and the reports mention that accessibility is active, but no further details.

• Firefox 92.0.1 Crash Report [@ PLDHashTable::Search | mozilla::a11y::AccAttributes::GetAttribute ]

Are you using accessibility devices on your computer ?

Do the crashes still happen in the current Beta 93.0 release (Beta is currently in release candidate stage and is scheduled for release next week) ?

• https://www.mozilla.org/en-US/firefox/all/#product-desktop-beta
• https://www.mozilla.org/en-US/firefox/beta/notes/

I know for a fact that I’ve had crashes with accessibility disabled. I think the reason why it’s showing it enabled/active right now is because I’ve reinstalled Firefox many times and deleted some Firefox data that was stored locally on my computer after I originally turned it off. Thus, it went back to the default (active).

To be honest I actually do have two accessibility related applications that I have running constantly. I definitely thought that it was a possibility that they could be a potential culprit in regards to the crashes. One of them is a buggy speech recognition software program (Dragon 6) which is no longer supported/maintained by the company who created it. I also have an eye tracking solution involving a hardware/software combo (the hardware is not compatible with Mac OS by default, somebody built custom software for Mac OS compatibility). The reason why I never mentioned these two things previously is because I absolutely need these two applications running at all times.

I havent tried beta 93 version. Trying it now, thank you.

Update: just had a crash on the beta 93 release

Please post the newest crash report.

As a test, disable the programs you talked about for a few hours.

3 most recent crash reports:

bp-2a23f5fa-59cc-4553-bb51-293d20210930

bp-41db14ba-6b4e-4683-8554-d498c0210930

bp-12c51526-821f-4b4f-9ac9-e62f70210930

I will try quitting out of those applications tomorrow for a little bit as I can’t do it at the moment. That being said, has there been any other information in my crash reports that has been helpful? You also mentioned previously that you “called for help”, any revelations from that?

Thank you for your continued help.

Product Firefox Release Channel beta Version 93.0rc1 Build ID 20210927210923 (2021-09-27)

bp-2a23f5fa-59cc-4553-bb51-293d20210930 bp-41db14ba-6b4e-4683-8554-d498c0210930 bp-12c51526-821f-4b4f-9ac9-e62f70210930

Signature: PLDHashTable::Search | mozilla::a11y::AccAttributes::GetAttribute

Crash Reason EXC_BAD_ACCESS / KERN_INVALID_ADDRESS

This is for Sumo's Related Bugs 1717501 NEW --- Crash in [@ PLDHashTable::Search | mozilla::a11y::AccAttributes::GetAttribute]

Just tried quitting out of the two accessibility related applications I mentioned above for 2 hours. No crashes, but that doesn't prove anything. I went like 6 hours without a crash a few days ago with both of those applications running. Like I said, I need them running at all times for the most part, so I can't really test for much longer and I would eventually have to launch them again no matter what. I may be able to replace the buggy Dragon dictation application but I don't want to do that unless there's evidence that it is the culprit for the crashes.

thank you for your continued help but I don't really understand what your posting from the crash reports Fred. If you pinpointed anything new from the crash reports or if you have access to anyone else who could help, please let me know. Thanks.

I had called for more help.

I got rid of the beta version that I tried for a day or two and then disabled the accessibility setting again and I now have not had even 1 crash in well over a week. Thank you both so much for helping. I know I did say I was willing to pay for help (and I still am) but after a quick google search I cannot find any information that provides me with some assurance that its safe to pay people on Venmo that you do not know. I wouldn't have been able to pay that much because I wanted to pay both of you but I atleast wanted to give something as a thank you. If you can provide me with adequate evidence of a safe method to pay you guys online, I will definitely consider that. thank you very much again and I apologize regarding the payment. Stephen

No pay is needed. We are here to help.

That was very good work. Well Done. Please flag your last post as Solved Problem as this can help others with similar problems. Go to that post and click the 'Solved' button to its right.

Ok Fred, I apologize again and thank you guys for you help.