On certain sites (in this case, the search page @ www.carmax.com) the entire browser will hang/crash (usually hang in an unresponsive state). The browser does not crash if accessibility.force_disable is set to 1. From what I can tell so far it might have to do with some aria attributes being set funny from JS but I am still looking into it.

I can reproduce the hang on 52.0b6[1] as well as Nightly54.0a1[2] [1] https://hg.mozilla.org/releases/mozilla-beta/rev/7b8aa893944b94d35e47314e52e0abff576c5ce2 Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Firefox/52.0 ID:20170213070939 [2] https://hg.mozilla.org/mozilla-central/rev/195049fabb7ac5709e5f75614ba630ba3d1b5a9b Mozilla/5.0 (Windows NT 10.0; WOW64; rv:54.0) Gecko/20100101 Firefox/54.0 ID:20170214030231 Steps to reproduce: 0. I am using Japanese IME ATOK2016 which activate a11y. 1. Open https://www.carmax.com/sell-my-car AR: Browser hang with bp-3dd7e932-8aa9-4993-82da-02b9e2170214, bp-a076addf-4619-4cd8-b83d-61b9a2170214

Additional information can be found here (how we ran into the bug): https://github.com/JedWatson/react-select/issues/1521

Update: unfortunately the carmax site has received a workaround for this issue so it'll no longer be recreateable there but the information on the github issue above should still be helpful.

Too late for firefox 52, mass-wontfix.

The percentage of ShutDownKill crashes with accessibility active roughly matches what we'd expect based on % of users that instantiate accessibility. It would be great to fix this but I'm not sure we have traction...

seems gone, no fresh crashes