This bug is for crash report bp-c9aae560-4139-4fa0-9172-d93720190628. ``` Top 10 frames of crashing thread: 0 xul.dll void mozilla::a11y::HyperTextProxyAccessibleWrap::GetNativeInterface accessible/windows/ProxyWrappers.h:49 1 xul.dll mozilla::a11y::AccessibleWrap::GetIAccessibleFor accessible/windows/msaa/AccessibleWrap.cpp:1374 2 xul.dll mozilla::a11y::AccessibleWrap::GetIAccessibleFor accessible/windows/msaa/AccessibleWrap.cpp:1374 3 xul.dll void mozilla::a11y::HyperTextProxyAccessibleWrap::GetNativeInterface accessible/windows/ProxyWrappers.h:49 4 xul.dll mozilla::a11y::AccessibleWrap::GetIAccessibleFor accessible/windows/msaa/AccessibleWrap.cpp:1374 5 xul.dll void mozilla::a11y::HyperTextProxyAccessibleWrap::GetNativeInterface accessible/windows/ProxyWrappers.h:49 6 xul.dll mozilla::a11y::AccessibleWrap::GetIAccessibleFor accessible/windows/msaa/AccessibleWrap.cpp:1374 7 xul.dll void mozilla::a11y::HyperTextProxyAccessibleWrap::GetNativeInterface accessible/windows/ProxyWrappers.h:49 8 xul.dll mozilla::a11y::AccessibleWrap::GetIAccessibleFor accessible/windows/msaa/AccessibleWrap.cpp:1374 9 xul.dll void mozilla::a11y::HyperTextProxyAccessibleWrap::GetNativeInterface accessible/windows/ProxyWrappers.h:49 ``` **Affected versions** * 69.0a1(2019-06-28) **Affected platforms** * Windows 10x64 aarch64 **Steps to reproduce** 1. Launch FF. 2. Go to about:config. 3. Set fission.autostart to True then restart the browser. 4. Go to any top website (eg: Netflix, Youtube, Reddit, Facebook, Pornhub, Twitter) **Expected result** * Reaching the website is done without any engine and stability issues( crashes and freezes) *Actual result** * Reaching any website will render various behaviors as follows: - After a while , the browser will enter a non responsive stat (Not Responding) and will ultimately crash. - Sometimes, it will crash simply when reaching any website. - **Regression range** * Will return with regression range ASAP **Another note:** - After a crash, when choosing to Restore, the page that will be loaded is the one previously accessed before the crash occurred.
Bug 1562208 Comment 0 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
This bug is for crash report bp-c9aae560-4139-4fa0-9172-d93720190628. ``` Top 10 frames of crashing thread: 0 xul.dll void mozilla::a11y::HyperTextProxyAccessibleWrap::GetNativeInterface accessible/windows/ProxyWrappers.h:49 1 xul.dll mozilla::a11y::AccessibleWrap::GetIAccessibleFor accessible/windows/msaa/AccessibleWrap.cpp:1374 2 xul.dll mozilla::a11y::AccessibleWrap::GetIAccessibleFor accessible/windows/msaa/AccessibleWrap.cpp:1374 3 xul.dll void mozilla::a11y::HyperTextProxyAccessibleWrap::GetNativeInterface accessible/windows/ProxyWrappers.h:49 4 xul.dll mozilla::a11y::AccessibleWrap::GetIAccessibleFor accessible/windows/msaa/AccessibleWrap.cpp:1374 5 xul.dll void mozilla::a11y::HyperTextProxyAccessibleWrap::GetNativeInterface accessible/windows/ProxyWrappers.h:49 6 xul.dll mozilla::a11y::AccessibleWrap::GetIAccessibleFor accessible/windows/msaa/AccessibleWrap.cpp:1374 7 xul.dll void mozilla::a11y::HyperTextProxyAccessibleWrap::GetNativeInterface accessible/windows/ProxyWrappers.h:49 8 xul.dll mozilla::a11y::AccessibleWrap::GetIAccessibleFor accessible/windows/msaa/AccessibleWrap.cpp:1374 9 xul.dll void mozilla::a11y::HyperTextProxyAccessibleWrap::GetNativeInterface accessible/windows/ProxyWrappers.h:49 ``` **Affected versions** * 69.0a1(2019-06-28) **Affected platforms** * Windows 10x64 aarch64 **Steps to reproduce** 1. Launch FF. 2. Go to about:config. 3. Set fission.autostart to True then restart the browser. 4. Go to any top website (eg: Netflix, Youtube, Reddit, Facebook, Pornhub, Twitter) **Expected result** * Reaching the website is done without any engine and stability issues( crashes and freezes) *Actual result** * Reaching any website will render various behaviors as follows: - After a while , the browser will enter a non responsive stat (Not Responding) and will ultimately crash. - Sometimes, it will crash simply when reaching any website. - **Regression range** * Will return with regression range ASAP **Another note:** - After a crash, when choosing to Restore, the page that will be loaded is the one previously accessed before the crash occurred. - The frequency of crashes on this platform makes it impossible for us to properly test.