1984989 - riscv64: Browser Tab Crash's upon Launch on Firefox 143

Status: UNCONFIRMED

(Core :: Graphics, defect)

Description

[Saiteja]

Attachment: Screenshot from 2025-08-25 11-59-48.png

User Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/139.0.0.0 Safari/537.36

Steps to reproduce:

Hello Team,

I have successfully built and installed the Beta Version of FireFox-v143 (git clone --branch FIREFOX_143_0b1_RELEASE --single-branch --depth 1 https://github.com/mozilla-firefox/firefox.git) on my riscv64 which does include the fixes for the bug - Bugzilla #1982266, provided to enable JIT for riscv64 system.

Actual results:

Upon successfully building the Firefox v143 in facing issue after launching the FireFox browser, Where i'm seeing the tabs are getting crashed directly upon launch of browser application. Not even a single tab is opening or found working while trying to surf the firefox-v143.

Expected results:

It would be really helpful, if someone can look into this issue since we found the Mozilla FireFox v143 would be expected to release sometime in Mid September which includes the support for JIT for riscv64, Could someone please help me to resolve this issue? And we can also provide any assistance or support needed for debug and testing, So we can have a working version to be ready with the JIT Support.

Regards,
Saiteja.B

Comment 1

[BugBot [:suhaib / :marco]]

The Bugbug bot thinks this bug should belong to the 'Core::JavaScript Engine: JIT' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.

Comment 2

[Saiteja]

Hi Team,
Please find the crash logs

~/firefox$ ./mach run
0:01.73 /home/user/firefox/obj-riscv64-unknown-linux-gnu/dist/bin/firefox -profile /home/user/firefox/obj-riscv64-unknown-linux-gnu/tmp/profile-default
Crash Annotation GraphicsCriticalError: |[0][GFX1-]: glxtest: DRM render node not clearly detectable. Falling back to using the only one that was found. (t=1.84459) [GFX1-]: glxtest: DRM render node not clearly detectable. Falling back to using the only one that was found.
Crash Annotation GraphicsCriticalError: |[0][GFX1-]: glxtest: DRM render node not clearly detectable. Falling back to using the only one that was found. (t=1.84459) |[1][GFX1-]: No GPUs detected via PCI
(t=1.84459) [GFX1-]: No GPUs detected via PCI

Crash Annotation GraphicsCriticalError: |[0][GFX1-]: glxtest: DRM render node not clearly detectable. Falling back to using the only one that was found. (t=1.84459) |[1][GFX1-]: No GPUs detected via PCI
(t=1.84459) |[2][GFX1-]: Failed to create EGLContext!: 0x300c (t=2.1006) [GFX1-]: Failed to create EGLContext!: 0x300c
Crash Annotation GraphicsCriticalError: |[0][GFX1-]: glxtest: DRM render node not clearly detectable. Falling back to using the only one that was found. (t=1.84459) |[1][GFX1-]: No GPUs detected via PCI
(t=1.84459) |[2][GFX1-]: Failed to create EGLContext!: 0x300c (t=2.1006) |[3][GFX1-]: Calling WaitFlushedEvent::Run: is delayed: 4644 (t=11.033) [GFX1-]: Calling WaitFlushedEvent::Run: is delayed: 4644
[Parent 1758, IPC I/O Parent] WARNING: process 1832 exited on signal 4: file /home/user/firefox/ipc/chromium/src/chrome/common/process_watcher_posix_sigchld.cc:134
console.error: AboutHomeStartupCache: "requestCache called with no _procManager!"
[Parent 1758, IPC I/O Parent] WARNING: process 1976 exited on signal 4: file /home/user/firefox/ipc/chromium/src/chrome/common/process_watcher_posix_sigchld.cc:134
[Parent 1758, IPC I/O Parent] WARNING: process 2022 exited on signal 4: file /home/user/firefox/ipc/chromium/src/chrome/common/process_watcher_posix_sigchld.cc:134
[Parent 1758, IPC I/O Parent] WARNING: process 1871 exited on signal 4: file /home/user/firefox/ipc/chromium/src/chrome/common/process_watcher_posix_sigchld.cc:134
[Parent 1758, IPC I/O Parent] WARNING: process 2097 exited on signal 4: file /home/user/firefox/ipc/chromium/src/chrome/common/process_watcher_posix_sigchld.cc:134
console.error: (new AbortError("Actor 'Thumbnails' destroyed before query 'Browser:Thumbnail:ContentInfo' was resolved", (void 0)))
console.error: (new AbortError("Actor 'Thumbnails' destroyed before query 'Browser:Thumbnail:ContentInfo' was resolved", (void 0)))
[Parent 1758, IPC I/O Parent] WARNING: process 2260 exited on signal 4: file /home/user/firefox/ipc/chromium/src/chrome/common/process_watcher_posix_sigchld.cc:134
JavaScript error: moz-src:///browser/components/tabbrowser/AsyncTabSwitcher.sys.mjs, line 380: TypeError: can't access property "schemeIs", requestedBrowser.currentURI is null
console.error: AboutHomeStartupCache: "requestCache called with no _procManager!"
JavaScript warning: https://www.google.com/js/th/9PTwBw1OM8z2Bs_CKh5--QK9dBvmMgOTEEdrdaBCaIo.js, line 3880: unreachable code after return statement
JavaScript warning: https://www.google.com/js/th/9PTwBw1OM8z2Bs_CKh5--QK9dBvmMgOTEEdrdaBCaIo.js, line 3880: unreachable code after return statement
JavaScript warning: https://www.google.com/js/th/9PTwBw1OM8z2Bs_CKh5--QK9dBvmMgOTEEdrdaBCaIo.js, line 3880: unreachable code after return statement
JavaScript warning: https://www.google.com/js/th/9PTwBw1OM8z2Bs_CKh5--QK9dBvmMgOTEEdrdaBCaIo.js, line 3880: unreachable code after return statement
JavaScript warning: https://www.google.com/js/th/9PTwBw1OM8z2Bs_CKh5--QK9dBvmMgOTEEdrdaBCaIo.js, line 3880: unreachable code after return statement
JavaScript warning: https://www.google.com/js/th/9PTwBw1OM8z2Bs_CKh5--QK9dBvmMgOTEEdrdaBCaIo.js, line 3880: unreachable code after return statement
JavaScript warning: https://www.google.com/js/th/9PTwBw1OM8z2Bs_CKh5--QK9dBvmMgOTEEdrdaBCaIo.js line 2 > eval, line 3880: unreachable code after return statement
JavaScript warning: https://www.google.com/js/th/9PTwBw1OM8z2Bs_CKh5--QK9dBvmMgOTEEdrdaBCaIo.js line 2 > eval, line 3880: unreachable code after return statement
JavaScript warning: https://www.google.com/js/th/9PTwBw1OM8z2Bs_CKh5--QK9dBvmMgOTEEdrdaBCaIo.js line 2 > eval, line 3880: unreachable code after return statement
JavaScript warning: https://www.google.com/js/th/9PTwBw1OM8z2Bs_CKh5--QK9dBvmMgOTEEdrdaBCaIo.js line 2 > eval, line 3880: unreachable code after return statement
JavaScript warning: https://www.google.com/js/th/9PTwBw1OM8z2Bs_CKh5--QK9dBvmMgOTEEdrdaBCaIo.js line 2 > eval, line 1: unreachable code after return statement
JavaScript warning: https://www.google.com/js/th/9PTwBw1OM8z2Bs_CKh5--QK9dBvmMgOTEEdrdaBCaIo.js line 2 > eval line 3880 > eval, line 1: unreachable code after return statement
JavaScript warning: https://www.google.com/js/th/9PTwBw1OM8z2Bs_CKh5--QK9dBvmMgOTEEdrdaBCaIo.js line 2 > eval, line 1: unreachable code after return statement
JavaScript warning: https://www.google.com/js/th/9PTwBw1OM8z2Bs_CKh5--QK9dBvmMgOTEEdrdaBCaIo.js line 2 > eval line 3880 > eval, line 1: unreachable code after return statement
JavaScript warning: https://www.google.com/js/th/9PTwBw1OM8z2Bs_CKh5--QK9dBvmMgOTEEdrdaBCaIo.js line 2 > eval, line 1: unreachable code after return statement
JavaScript warning: https://www.google.com/js/th/9PTwBw1OM8z2Bs_CKh5--QK9dBvmMgOTEEdrdaBCaIo.js line 2 > eval line 3880 > eval, line 1: unreachable code after return statement
[Parent 1758, IPC I/O Parent] WARNING: process 2176 exited on signal 4: file /home/user/firefox/ipc/chromium/src/chrome/common/process_watcher_posix_sigchld.cc:134
[Parent 1758, IPC I/O Parent] WARNING: process 2314 exited on signal 4: file /home/user/firefox/ipc/chromium/src/chrome/common/process_watcher_posix_sigchld.cc:134
console.error: AboutHomeStartupCache: "requestCache called with no _procManager!"
console.error: AboutHomeStartupCache: "requestCache called with no _procManager!"
[Parent 1758, IPC I/O Parent] WARNING: process 2576 exited on signal 4: file /home/user/firefox/ipc/chromium/src/chrome/common/process_watcher_posix_sigchld.cc:134
console.error: "Given tab is not restoring."
[Parent 1758, IPC I/O Parent] WARNING: process 2356 exited on signal 4: file /home/user/firefox/ipc/chromium/src/chrome/common/process_watcher_posix_sigchld.cc:134
JavaScript warning: https://www.google.com/js/th/9PTwBw1OM8z2Bs_CKh5--QK9dBvmMgOTEEdrdaBCaIo.js, line 2338: unreachable code after return statement
JavaScript warning: https://www.google.com/js/th/9PTwBw1OM8z2Bs_CKh5--QK9dBvmMgOTEEdrdaBCaIo.js, line 2338: unreachable code after return statement
JavaScript warning: https://www.google.com/js/th/9PTwBw1OM8z2Bs_CKh5--QK9dBvmMgOTEEdrdaBCaIo.js, line 2338: unreachable code after return statement
JavaScript warning: https://www.google.com/js/th/9PTwBw1OM8z2Bs_CKh5--QK9dBvmMgOTEEdrdaBCaIo.js, line 2338: unreachable code after return statement
JavaScript warning: https://www.google.com/js/th/9PTwBw1OM8z2Bs_CKh5--QK9dBvmMgOTEEdrdaBCaIo.js, line 2338: unreachable code after return statement
JavaScript warning: https://www.google.com/js/th/9PTwBw1OM8z2Bs_CKh5--QK9dBvmMgOTEEdrdaBCaIo.js, line 2338: unreachable code after return statement
JavaScript warning: https://www.google.com/js/th/9PTwBw1OM8z2Bs_CKh5--QK9dBvmMgOTEEdrdaBCaIo.js line 2 > eval, line 2338: unreachable code after return statement
JavaScript warning: https://www.google.com/js/th/9PTwBw1OM8z2Bs_CKh5--QK9dBvmMgOTEEdrdaBCaIo.js line 2 > eval, line 2338: unreachable code after return statement
JavaScript warning: https://www.google.com/js/th/9PTwBw1OM8z2Bs_CKh5--QK9dBvmMgOTEEdrdaBCaIo.js line 2 > eval, line 2338: unreachable code after return statement
JavaScript warning: https://www.google.com/js/th/9PTwBw1OM8z2Bs_CKh5--QK9dBvmMgOTEEdrdaBCaIo.js line 2 > eval, line 2338: unreachable code after return statement
JavaScript warning: https://www.google.com/js/th/9PTwBw1OM8z2Bs_CKh5--QK9dBvmMgOTEEdrdaBCaIo.js line 2 > eval, line 1: unreachable code after return statement
JavaScript warning: https://www.google.com/js/th/9PTwBw1OM8z2Bs_CKh5--QK9dBvmMgOTEEdrdaBCaIo.js line 2 > eval line 2338 > eval, line 1: unreachable code after return statement
JavaScript warning: https://www.google.com/js/th/9PTwBw1OM8z2Bs_CKh5--QK9dBvmMgOTEEdrdaBCaIo.js line 2 > eval, line 1: unreachable code after return statement
JavaScript warning: https://www.google.com/js/th/9PTwBw1OM8z2Bs_CKh5--QK9dBvmMgOTEEdrdaBCaIo.js line 2 > eval line 2338 > eval, line 1: unreachable code after return statement
JavaScript warning: https://www.google.com/js/th/9PTwBw1OM8z2Bs_CKh5--QK9dBvmMgOTEEdrdaBCaIo.js line 2 > eval line 2338 > eval, line 1: unreachable code after return statement
JavaScript warning: https://www.google.com/js/th/9PTwBw1OM8z2Bs_CKh5--QK9dBvmMgOTEEdrdaBCaIo.js line 2 > eval line 2338 > eval line 1 > eval, line 1: unreachable code after return statement
JavaScript warning: https://www.google.com/js/th/9PTwBw1OM8z2Bs_CKh5--QK9dBvmMgOTEEdrdaBCaIo.js line 2 > eval, line 2338: unreachable code after return statement
JavaScript warning: https://www.google.com/js/th/9PTwBw1OM8z2Bs_CKh5--QK9dBvmMgOTEEdrdaBCaIo.js line 2 > eval, line 2338: unreachable code after return statement
JavaScript warning: https://www.google.com/js/th/9PTwBw1OM8z2Bs_CKh5--QK9dBvmMgOTEEdrdaBCaIo.js line 2 > eval line 2338 > eval line 1 > eval, line 1: unreachable code after return statement
JavaScript warning: https://www.google.com/js/th/9PTwBw1OM8z2Bs_CKh5--QK9dBvmMgOTEEdrdaBCaIo.js line 2 > eval line 2338 > eval line 1 > eval, line 1: unreachable code after return statement
JavaScript warning: https://www.google.com/js/th/9PTwBw1OM8z2Bs_CKh5--QK9dBvmMgOTEEdrdaBCaIo.js line 2 > eval line 2338 > eval line 1 > eval, line 1: unreachable code after return statement
JavaScript warning: https://www.google.com/js/th/9PTwBw1OM8z2Bs_CKh5--QK9dBvmMgOTEEdrdaBCaIo.js line 2 > eval line 2338 > eval line 1 > eval line 1 > eval, line 1: unreachable code after return statement
JavaScript warning: https://www.google.com/js/th/9PTwBw1OM8z2Bs_CKh5--QK9dBvmMgOTEEdrdaBCaIo.js line 2 > eval line 2338 > eval line 1 > eval line 1 > eval, line 1: unreachable code after return statement
JavaScript warning: https://www.google.com/js/th/9PTwBw1OM8z2Bs_CKh5--QK9dBvmMgOTEEdrdaBCaIo.js line 2 > eval line 2338 > eval line 1 > eval line 1 > eval, line 1: unreachable code after return statement
GetShaderInfoLog() ->
Compile failed.
ERROR: 0:2: Extension GL_EXT_frag_depth not supported
1 compilation errors. No code generated.

GetShaderSource() ->

#extension GL_EXT_frag_depth: require
void main() {}

[Parent 1758, IPC I/O Parent] WARNING: process 2360 exited on signal 4: file /home/user/firefox/ipc/chromium/src/chrome/common/process_watcher_posix_sigchld.cc:134
JavaScript error: moz-src:///browser/components/tabbrowser/AsyncTabSwitcher.sys.mjs, line 380: TypeError: can't access property "schemeIs", requestedBrowser.currentURI is null
JavaScript warning: https://www.google.com/js/th/9PTwBw1OM8z2Bs_CKh5--QK9dBvmMgOTEEdrdaBCaIo.js, line 7340: unreachable code after return statement
JavaScript warning: https://www.google.com/js/th/9PTwBw1OM8z2Bs_CKh5--QK9dBvmMgOTEEdrdaBCaIo.js, line 7340: unreachable code after return statement
JavaScript warning: https://www.google.com/js/th/9PTwBw1OM8z2Bs_CKh5--QK9dBvmMgOTEEdrdaBCaIo.js, line 7340: unreachable code after return statement
JavaScript warning: https://www.google.com/js/th/9PTwBw1OM8z2Bs_CKh5--QK9dBvmMgOTEEdrdaBCaIo.js, line 7340: unreachable code after return statement
JavaScript warning: https://www.google.com/js/th/9PTwBw1OM8z2Bs_CKh5--QK9dBvmMgOTEEdrdaBCaIo.js, line 7340: unreachable code after return statement
JavaScript warning: https://www.google.com/js/th/9PTwBw1OM8z2Bs_CKh5--QK9dBvmMgOTEEdrdaBCaIo.js, line 7340: unreachable code after return statement
JavaScript warning: https://www.google.com/js/th/9PTwBw1OM8z2Bs_CKh5--QK9dBvmMgOTEEdrdaBCaIo.js line 2 > eval, line 7340: unreachable code after return statement
JavaScript warning: https://www.google.com/js/th/9PTwBw1OM8z2Bs_CKh5--QK9dBvmMgOTEEdrdaBCaIo.js line 2 > eval, line 7340: unreachable code after return statement
JavaScript warning: https://www.google.com/js/th/9PTwBw1OM8z2Bs_CKh5--QK9dBvmMgOTEEdrdaBCaIo.js line 2 > eval, line 7340: unreachable code after return statement
JavaScript warning: https://www.google.com/js/th/9PTwBw1OM8z2Bs_CKh5--QK9dBvmMgOTEEdrdaBCaIo.js line 2 > eval, line 7340: unreachable code after return statement
JavaScript warning: https://www.google.com/js/th/9PTwBw1OM8z2Bs_CKh5--QK9dBvmMgOTEEdrdaBCaIo.js line 2 > eval line 7340 > eval, line 1: unreachable code after return statement
JavaScript warning: https://www.google.com/js/th/9PTwBw1OM8z2Bs_CKh5--QK9dBvmMgOTEEdrdaBCaIo.js line 2 > eval line 7340 > eval line 1 > eval, line 1: unreachable code after return statement
JavaScript warning: https://www.google.com/js/th/9PTwBw1OM8z2Bs_CKh5--QK9dBvmMgOTEEdrdaBCaIo.js line 2 > eval line 7340 > eval, line 1: unreachable code after return statement
JavaScript warning: https://www.google.com/js/th/9PTwBw1OM8z2Bs_CKh5--QK9dBvmMgOTEEdrdaBCaIo.js line 2 > eval line 7340 > eval line 1 > eval, line 1: unreachable code after return statement
JavaScript warning: https://www.google.com/js/th/9PTwBw1OM8z2Bs_CKh5--QK9dBvmMgOTEEdrdaBCaIo.js line 2 > eval line 7340 > eval, line 1: unreachable code after return statement
JavaScript warning: https://www.google.com/js/th/9PTwBw1OM8z2Bs_CKh5--QK9dBvmMgOTEEdrdaBCaIo.js line 2 > eval line 7340 > eval line 1 > eval, line 1: unreachable code after return statement
JavaScript warning: https://www.google.com/js/th/9PTwBw1OM8z2Bs_CKh5--QK9dBvmMgOTEEdrdaBCaIo.js line 2 > eval, line 7340: unreachable code after return statement
JavaScript warning: https://www.google.com/js/th/9PTwBw1OM8z2Bs_CKh5--QK9dBvmMgOTEEdrdaBCaIo.js line 2 > eval, line 7340: unreachable code after return statement
JavaScript warning: https://www.google.com/js/th/9PTwBw1OM8z2Bs_CKh5--QK9dBvmMgOTEEdrdaBCaIo.js line 2 > eval line 7340 > eval line 1 > eval, line 1: unreachable code after return statement
JavaScript warning: https://www.google.com/js/th/9PTwBw1OM8z2Bs_CKh5--QK9dBvmMgOTEEdrdaBCaIo.js line 2 > eval line 7340 > eval line 1 > eval, line 1: unreachable code after return statement
JavaScript warning: https://www.google.com/js/th/9PTwBw1OM8z2Bs_CKh5--QK9dBvmMgOTEEdrdaBCaIo.js line 2 > eval line 7340 > eval line 1 > eval, line 1: unreachable code after return statement
JavaScript warning: https://www.google.com/js/th/9PTwBw1OM8z2Bs_CKh5--QK9dBvmMgOTEEdrdaBCaIo.js line 2 > eval line 7340 > eval line 1 > eval line 1 > eval, line 1: unreachable code after return statement
JavaScript warning: https://www.google.com/js/th/9PTwBw1OM8z2Bs_CKh5--QK9dBvmMgOTEEdrdaBCaIo.js line 2 > eval line 7340 > eval line 1 > eval line 1 > eval, line 1: unreachable code after return statement
JavaScript warning: https://www.google.com/js/th/9PTwBw1OM8z2Bs_CKh5--QK9dBvmMgOTEEdrdaBCaIo.js line 2 > eval line 7340 > eval line 1 > eval line 1 > eval, line 1: unreachable code after return statement
GetShaderInfoLog() ->
Compile failed.
ERROR: 0:2: Extension GL_EXT_frag_depth not supported
1 compilation errors. No code generated.

GetShaderSource() ->

#extension GL_EXT_frag_depth: require
void main() {}

[Parent 1758, IPC I/O Parent] WARNING: process 2658 exited on signal 4: file /home/user/firefox/ipc/chromium/src/chrome/common/process_watcher_posix_sigchld.cc:134

Comment 3

[Rong Bao [:csmantle]]

I'm not sure where to start looking. The logs doesn't mention SM components, apart from some SIGCHLD. Jan, do you think these GraphicsCriticalErrors have anything to do with this? Or some other suggestions?

Comment 4

[Jan de Mooij [:jandem]]

Saiteja, can you reproduce this with a clean profile? What makes you think this is related to the JIT support?

Which riscv64 CPU/machine are you using?

Comment 5

[Saiteja]

Hi Jan,

I have built the Firefox-v143 without making any changes to original code base and notice the tabs are getting crashed upon launch although i am not sure , what may be the reason that could be crashing the tabs.

I am on U740 Quad Core CPU.

Regards,
Saiteja

Comment 6

[Jan de Mooij [:jandem]]

You could try deleting this line in js/moz.configure to disable the JIT by default for riscv64, and then do another ./mach build to see if that helps.

Comment 7

[Saiteja]

Hi Jan, Thanks for the reply.

As you suggested, I will try to remove "riscv64" target and rebuild the Firefox-v143.

I would like to understand why is it required the remove the target riscv64 in js/moz.configure? Does it mean now the FireFox will re-build by disabling the JIT? I would like to how we can build the FireFox 143 with JIT enabled, since i'm looking to have the best browser performance (without lags) for riscv64. This is something i've been working for a long time to improve the performance.

I've the necessary hardware for riscv64, let me know if you need more support on getting it working for riscv64 so can provide support for resolving any issues that might arise with testing firefox.

Regards,
Saiteja.

Comment 8

[Rong Bao [:csmantle]]

Hi Sai Teja,

(In reply to Saiteja from comment #7)

I would like to understand why is it required the remove the target riscv64 in js/moz.configure?

That helps us to pinpoint the component causing the crash. If v143 works when JIT is disabled but breaks when it is enabled, we would be certain that JIT is causing issues. Otherwise, the crash might be attributed to other components.

Hope it helps.

Comment 9

[Saiteja]

Ok Thanks , Currently I removed riscv64 target and rebuilding the Firefox.

Once it done, i will check and share you the results.

Regards,
Saiteja.

Comment 10

[Saiteja]

Hi Jan and Rong,

We verifed the Firefox-v143 with excluding the target riscv64 in js/moz.configure, but we are still observing tabs are getting crashed frequently and we are unable to perform surfing.

Regards,
Saiteja.

Comment 11

[Rong Bao [:csmantle]]

In that case, should we re-evaluate whether this bug still fits in the "JIT" component category?

Comment 12

[Jan de Mooij [:jandem]]

Saiteja, you could try a debug build to see if that gives us more information.

To do that, create a mozconfig-dbg file with this in it:

mk_add_options MOZ_OBJDIR=@TOPSRCDIR@/obj-ff-dbg
ac_add_options --enable-debug

Then to do a build using this file (change to use the right file path):

export MOZCONFIG=/path/to/mozconfig-dbg
./mach build
./mach run

Comment 13

[Jan de Mooij [:jandem]]

(In reply to Rong Bao [:csmantle] from comment #11)

In that case, should we re-evaluate whether this bug still fits in the "JIT" component category?

I can move it to Core: General for now.

Comment 14

[Saiteja]

Hi, Jan and Rong

As you suggested, we added debug config in the Firefox and we have built with the same for firefox-v143-b1. we also noticed v143-b5 release so we also included the debug flags and tried to build the firefox with debug config enabled.

Below are the observations:

Firefox-v143-b1:

• observing tabs getting crash frequently and unable to perform web surfing.
• debug logs attached as - Firefox-v143-b1-debug.txt

Firefox-v143-b5:

• observing tabs getting crash spordically and able to perform the web surfing after restoring the tab each time.
• debug logs attached as - Firefox-v143-b5-debug.txt

can someone please look into this issue and have this issue resolved at the earliest or provide us the fix/patch. so we can try to test the fixes/patches, which can help the community team as well.

Regards,
Saiteja

Comment 15

[Saiteja]

Attachment: Firefox-v143-b1-debug.txt

Comment 16

[Saiteja]

Attachment: Firefox-v143-b5-debug.txt

Comment 17

[Rong Bao [:csmantle]]

Hi Saiteja, Thanks for the log.

Actually, I still don't see the crash's relevance to JIT: the only direct mention of JS is JavaScript error: , line 0: Error: Type error for platformInfo value (Error processing arch: Invalid enumeration value "riscv64") for runtime.getPlatformInfo. Other logs seem to talk about graphics, layout and audio, so I'm sorry I can't help much on those.

I'm needinfo-ing Jan for that getPlatformInfo error. I think we also need to find the right person to look into rest of the logs, so needinfo-ing :glob ✱ as well.

Comment 18

[Jan de Mooij [:jandem]]

(In reply to Rong Bao [:csmantle] from comment #17)

I'm needinfo-ing Jan for that getPlatformInfo error.

This might be because we're missing riscv64 in the list here but I'm not sure.

What we need for the crash is a stack trace from the debugger. Saiteja, maybe you can attach gdb to the content process for that (see instructions here) and get a back trace when it crashes.

Comment 19

[Rong Bao [:csmantle]]

(In reply to Jan de Mooij [:jandem] from comment #18)

This might be because we're missing riscv64 in the list here but I'm not sure.

That's interesting, I wonder if loong64 and mips64 have the same problem. I'm filing another bug to add riscv64 to the list.

Comment 20

[:glob ✱]

Over to Graphics for investigation.

Comment 21

[Saiteja]

Hello Rang Bao, Thanks for the reply.

I notice there is a bug #1985988, added which looks to be a fix for JavaScript error: , line 0: Error: Type error for platformInfo value (Error processing arch: Invalid enumeration value "riscv64") for runtime.getPlatformInfo. So will try to check the patch you've added into the bug #1985988, and verify it on top of Mozilla Firefox 143-b5 release on my RISCV64 System and share you the update on this.

Regards,
Saiteja

Comment 22

[Rong Bao [:csmantle]]

(In reply to Saiteja from comment #21)

So will try to check the patch you've added into the bug #1985988, and verify it on top of Mozilla Firefox 143-b5 release on my RISCV64 System and share you the update on this.

Glad to hear that. In case you have something to share about that bug in particular, you can add bug 1985988 to this one's See Also field for xref, and redirect related discussions there.

But I still doubt that bug is the cause. We have many users running FF on LoongArch64 and MIPS64, both of which are not included in the list mentioned in bug 1985988.

Comment 23

[BugBot [:suhaib / :marco]]

The severity field is not set for this bug.
:bhood, could you have a look please?

For more information, please visit BugBot documentation.

Comment 24

[Saiteja]

Hi Team,

We've tried building FFx-v143 on my RISC-V Development Platform with Ubuntu 22.04, But after building the FFx-143 we're noticing Tab are getting Crashed upon Launching the FireFox Browser.

Please find the attached screenshot and logs.

Log:-
Ubuntu-riscv64:~/firefox$ ./mach run
0:01.68 /home/user/firefox/obj-riscv64-unknown-linux-gnu/dist/bin/firefox -profile /home/user/firefox/obj-riscv64-unknown-linux-gnu/tmp/profile-default
Crash Annotation GraphicsCriticalError: |[0][GFX1-]: glxtest: DRM render node not clearly detectable. Falling back to using the only one that was found. (t=1.62145) [GFX1-]: glxtest: DRM render node not clearly detectable. Falling back to using the only one that was found.
Crash Annotation GraphicsCriticalError: |[0][GFX1-]: glxtest: DRM render node not clearly detectable. Falling back to using the only one that was found. (t=1.62145) |[1][GFX1-]: No GPUs detected via PCI
(t=1.62145) [GFX1-]: No GPUs detected via PCI

Crash Annotation GraphicsCriticalError: |[0][GFX1-]: glxtest: DRM render node not clearly detectable. Falling back to using the only one that was found. (t=1.62145) |[1][GFX1-]: No GPUs detected via PCI
(t=1.62145) |[2][GFX1-]: Failed to create EGLContext!: 0x300c (t=1.85346) [GFX1-]: Failed to create EGLContext!: 0x300c
Crash Annotation GraphicsCriticalError: |[0][GFX1-]: glxtest: DRM render node not clearly detectable. Falling back to using the only one that was found. (t=1.62145) |[1][GFX1-]: No GPUs detected via PCI
(t=1.62145) |[2][GFX1-]: Failed to create EGLContext!: 0x300c (t=1.85346) |[3][GFX1-]: Calling WaitFlushedEvent::Run: is delayed: 3974 (t=9.24177) [GFX1-]: Calling WaitFlushedEvent::Run: is delayed: 3974
[Parent 84932, IPC I/O Parent] WARNING: process 85005 exited on signal 4: file /home/user/firefox/ipc/chromium/src/chrome/common/process_watcher_posix_sigchld.cc:134
console.error: (new InvalidStateError("An attempt was made to use an object that is not, or is no longer, usable", (void 0), 415))
console.error: (new InvalidStateError("JSWindowActorParent.sendAsyncMessage: JSWindowActorParent cannot send at the moment", (void 0), 529))
console.error: AboutHomeStartupCache: "requestCache called with no _procManager!"
[Parent 84932, IPC I/O Parent] WARNING: process 85150 exited on signal 4: file /home/user/firefox/ipc/chromium/src/chrome/common/process_watcher_posix_sigchld.cc:134
console.error: AboutHomeStartupCache: "requestCache called with no _procManager!"
console.error: AboutHomeStartupCache: "requestCache called with no _procManager!"
Crash Annotation GraphicsCriticalError: |[0][GFX1-]: glxtest: DRM render node not clearly detectable. Falling back to using the only one that was found. (t=1.62145) |[1][GFX1-]: No GPUs detected via PCI
(t=1.62145) |[2][GFX1-]: Failed to create EGLContext!: 0x300c (t=1.85346) |[3][GFX1-]: Calling WaitFlushedEvent::Run: is delayed: 3974 (t=9.24177) |[4][GFX1-]: RenderCompositorSWGL failed mapping default framebuffer, no dt (t=521.447) [GFX1-]: RenderCompositorSWGL failed mapping default framebuffer, no dt
[Parent 84932, IPC I/O Parent] WARNING: process 85272 exited on signal 4: file /home/user/firefox/ipc/chromium/src/chrome/common/process_watcher_posix_sigchld.cc:134
console.error: AboutHomeStartupCache: "requestCache called with no _procManager!"
[Parent 84932, IPC I/O Parent] WARNING: process 85358 exited on signal 4: file /home/user/firefox/ipc/chromium/src/chrome/common/process_watcher_posix_sigchld.cc:134
console.error: AboutHomeStartupCache: "requestCache called with no _procManager!"
console.error: AboutHomeStartupCache: "requestCache called with no _procManager!"
console.error: AboutHomeStartupCache: "requestCache called with no _procManager!"
console.error: AboutHomeStartupCache: "requestCache called with no _procManager!"
console.error: AboutHomeStartupCache: "requestCache called with no _procManager!"
Exiting due to channel error.
Exiting due to channel error.
Exiting due to channel error.
Exiting due to channel error.
Exiting due to channel error.
Ubuntu-riscv64:~/firefox$

Regards,
Saiteja.

Comment 25

[Saiteja]

Attachment: Firefox-143-tabs-crash.png

Comment 26

[Saiteja]

Hi Team,
I've built the beta version of Firefox-v144 on riscv64 board.
But upon launching the browser tabs are getting crashed as same as Firefox-v143.
Could someone please look into resolving this issue of crashing tabs on Firefox from v143.

Regards,
Saiteja.

Comment 27

[Timothy Nikkel (:tnikkel)]

Do you get a crash stack at all? If you goto about:crashes is there anything there? (Apologies if this is covered in this bug already, I only skimmed it)

Comment 28

[Saiteja]

Hi Timothy,
This is the crash log that i am facing.
Log:-
Ubuntu-riscv64:~/firefox$ ./mach run
0:01.68 /home/user/firefox/obj-riscv64-unknown-linux-gnu/dist/bin/firefox -profile /home/user/firefox/obj-riscv64-unknown-linux-gnu/tmp/profile-default
Crash Annotation GraphicsCriticalError: |[0][GFX1-]: glxtest: DRM render node not clearly detectable. Falling back to using the only one that was found. (t=1.62145) [GFX1-]: glxtest: DRM render node not clearly detectable. Falling back to using the only one that was found.
Crash Annotation GraphicsCriticalError: |[0][GFX1-]: glxtest: DRM render node not clearly detectable. Falling back to using the only one that was found. (t=1.62145) |[1][GFX1-]: No GPUs detected via PCI
(t=1.62145) [GFX1-]: No GPUs detected via PCI

Crash Annotation GraphicsCriticalError: |[0][GFX1-]: glxtest: DRM render node not clearly detectable. Falling back to using the only one that was found. (t=1.62145) |[1][GFX1-]: No GPUs detected via PCI
(t=1.62145) |[2][GFX1-]: Failed to create EGLContext!: 0x300c (t=1.85346) [GFX1-]: Failed to create EGLContext!: 0x300c
Crash Annotation GraphicsCriticalError: |[0][GFX1-]: glxtest: DRM render node not clearly detectable. Falling back to using the only one that was found. (t=1.62145) |[1][GFX1-]: No GPUs detected via PCI
(t=1.62145) |[2][GFX1-]: Failed to create EGLContext!: 0x300c (t=1.85346) |[3][GFX1-]: Calling WaitFlushedEvent::Run: is delayed: 3974 (t=9.24177) [GFX1-]: Calling WaitFlushedEvent::Run: is delayed: 3974
[Parent 84932, IPC I/O Parent] WARNING: process 85005 exited on signal 4: file /home/user/firefox/ipc/chromium/src/chrome/common/process_watcher_posix_sigchld.cc:134
console.error: (new InvalidStateError("An attempt was made to use an object that is not, or is no longer, usable", (void 0), 415))
console.error: (new InvalidStateError("JSWindowActorParent.sendAsyncMessage: JSWindowActorParent cannot send at the moment", (void 0), 529))
console.error: AboutHomeStartupCache: "requestCache called with no _procManager!"
[Parent 84932, IPC I/O Parent] WARNING: process 85150 exited on signal 4: file /home/user/firefox/ipc/chromium/src/chrome/common/process_watcher_posix_sigchld.cc:134
console.error: AboutHomeStartupCache: "requestCache called with no _procManager!"
console.error: AboutHomeStartupCache: "requestCache called with no _procManager!"
Crash Annotation GraphicsCriticalError: |[0][GFX1-]: glxtest: DRM render node not clearly detectable. Falling back to using the only one that was found. (t=1.62145) |[1][GFX1-]: No GPUs detected via PCI
(t=1.62145) |[2][GFX1-]: Failed to create EGLContext!: 0x300c (t=1.85346) |[3][GFX1-]: Calling WaitFlushedEvent::Run: is delayed: 3974 (t=9.24177) |[4][GFX1-]: RenderCompositorSWGL failed mapping default framebuffer, no dt (t=521.447) [GFX1-]: RenderCompositorSWGL failed mapping default framebuffer, no dt
[Parent 84932, IPC I/O Parent] WARNING: process 85272 exited on signal 4: file /home/user/firefox/ipc/chromium/src/chrome/common/process_watcher_posix_sigchld.cc:134
console.error: AboutHomeStartupCache: "requestCache called with no _procManager!"
[Parent 84932, IPC I/O Parent] WARNING: process 85358 exited on signal 4: file /home/user/firefox/ipc/chromium/src/chrome/common/process_watcher_posix_sigchld.cc:134
console.error: AboutHomeStartupCache: "requestCache called with no _procManager!"
console.error: AboutHomeStartupCache: "requestCache called with no _procManager!"
console.error: AboutHomeStartupCache: "requestCache called with no _procManager!"
console.error: AboutHomeStartupCache: "requestCache called with no _procManager!"
console.error: AboutHomeStartupCache: "requestCache called with no _procManager!"
Exiting due to channel error.
Exiting due to channel error.
Exiting due to channel error.
Exiting due to channel error.
Exiting due to channel error.
Ubuntu-riscv64:~/firefox$

about:crashes is the invalid url.

Regards,
Saiteja.

Comment 30

[Saiteja]

Hi Martin, Rong & Jan,

Can you please let us know if you have investigated this crash further ? As we are unable to proceed the build from Firefox-v143 and above, as we are noticing browser tabs crash issues are occuring consistently on every release .
Can you please help us to share a fix for the same?

Regards,
Saiteja.B

Comment 31

[Jim Mathies [:jimm]]

Attachment: bug-1984989-triage.md

Interesting analysis and summary of this bug courtesy of a triage tool I've been working on in Claude. Helps to summarize everything here.