5 ms·

Unfortunately those crashes do not appear to be related to low memory scenarios. They seem to be genuine bugs in the screen reader. I think the right bug tracki

Unfortunately those crashes do not appear to be related to low memory scenarios. They seem to be genuine bugs in the screen reader. I think the right bug tracking them is this one: https://bugzilla.mozilla.org/show_bug.cgi?id=1691928 https://bugzilla.mozilla.org/show_bug.cgi?id=1691928

gostsamo 5y ago
As I said, usually I don't wait for a full crash so there is a survival bias in those ids.
- gcp 5y ago
  The original ticket seems to indicate this is a leak in a Windows accessibility service and so far there was no luck in finding a way to avoid it. That sucks.
  - gostsamo 5y ago
    Well, if I'd like to have something rewritten in rust, this would be my first choice. :)