Closed Bug 1969395 Opened 5 months ago Closed 4 months ago

Firefox 139 crashes at startup on LoongArch64

Categories

(Core :: JavaScript Engine: JIT, defect, P5)

Product:
Core
Component:
JavaScript Engine: JIT
Version:
Firefox 139
Platform:
Other
Linux
Type:
defect

Tracking

()

Status:
RESOLVED FIXED
Milestone:
140 Branch
Tracking Flags:
Tracking Status
firefox-esr128 --- unaffected
firefox139 --- fixed
firefox140 --- fixed

People

(Reporter: xen0n, Assigned: zhaojiazhong-hf)

References

(Blocks 2 open bugs, Regression)

Details

(Keywords: regression)

Bug 1961587 actually regressed the 139 branch to the point of straight crashes at startup, but was not uplifted so vanilla Firefox 139.0 no longer starts on LoongArch64. MIPS64 and RISCV64 are likely also affected but I don't have test hardware of either handy at present.

According to my experiments, backporting D248134 and D248862 fixes the crash, so we would like the changes backported to 139 branch.

Blocks: 1746335
Keywords: regression
OS: Unspecified → Linux
Regressed by: 1961587
Hardware: Unspecified → Other
See Also: → https://github.com/loongson-community/discussions/issues/93
Version: unspecified → Firefox 139
Regressed by: 1944761
Depends on: 1961587
No longer regressed by: 1961587

:debadree333, since you are the author of the regressor, bug 1944761, could you take a look?

For more information, please visit BugBot documentation.

Flags: needinfo?(debadree333)

It turns out that a backport is necessary after all. Otherwise, an attempt to launch Firefox would result in an immediate segfault.

Flags: needinfo?(iireland)

I've requested uplift on the two relevant patches.

Flags: needinfo?(iireland)
Flags: needinfo?(debadree333)
Blocks: sm-loong-arch64
Severity: -- → S3
Priority: -- → P5

Fixed in Firefox 139.0.4 with uplift change https://phabricator.services.mozilla.com/D252534, but I cannot mark as RESOLVED+FIXED.

Status: UNCONFIRMED → RESOLVED
Closed: 4 months ago
Resolution: --- → FIXED

Set release status flags based on info from the regressing bug 1944761

status-firefox139: --- → affected
status-firefox140: --- → affected
status-firefox141: --- → affected
status-firefox-esr128: --- → unaffected
Assignee: nobody → zhaojiazhong-hf
status-firefox139: affected → fixed
status-firefox140: affected → fixed
status-firefox141: affected → ---
Target Milestone: --- → 140 Branch
You need to log in before you can comment on or make changes to this bug.