Tab crashes on mips64
Categories
(Core :: JavaScript Engine: JIT, defect, P5)
Tracking
()
People
(Reporter: vinceying113, Unassigned)
References
(Regression)
Details
(Keywords: regression)
User Agent: Mozilla/5.0 (X11; Linux mips64; rv:68.0) Gecko/20100101 Firefox/68.0
Steps to reproduce:
https://twitter.com/firefox will tab crash within a minute of use (if I start scrolling down it will eventually crash). Disabling javascript.options.baselinejit seems to eliminate the issue.
Actual results:
Tab crash.
Expected results:
Works fine on other architectures (x64, arm64).
Reporter | ||
Comment 1•4 years ago
|
||
Bug occurs in 78.5esr.
Comment 2•4 years ago
|
||
Firefox on MIPS is a Tier 3 platform:
If you’re filing a bug against Firefox on a Tier-3 platform (or any combination of OS, CPU and compiler not listed above) please bear in mind that Mozilla developers do not reliably have access to non-Tier-1 platforms or build environments. To be actionable bug reports against non-Tier-1 platforms should include as much information as possible to help the owner of the bug determine the cause of the problem and the proper solution. If you can provide a patch, a regression range or assist in verifying that the developer’s patches work for your platform, that would help a lot towards getting your bugs fixed and checked into the tree.
If you can capture a stack trace, we can take a look. We will accept a patch if you can provide one. However, we do not have the resources to solve this bug ourselves.
Your Linux distribution may be able to offer more support. (From the link above: "Linux on various CPU architectures including ARM variants not listed above, PowerPC, and x86 CPUs without SSE2 support - maintained by various Linux distributions")
Otherwise, disabling the JITs will hurt performance but should prevent crashes. If you still see occasional crashes with javascript.options.baselinejit
set to false, try javascript.options.blinterp
.
Good luck!
Comment 3•4 years ago
|
||
Thanks for your information! I reproduced it on 78.4esr, and I will try to find out the bug.
Comment 4•4 years ago
|
||
It seems like to be caused by bug 1639896, which is resolved in firefox79. I will see if it can be merged into firefox-esr78.
Updated•4 years ago
|
Updated•3 years ago
|
Updated•6 days ago
|
Description
•