[Bug]: the command "firefox -headless" crashes with Segmentation fault #22286
Labels
bug report
Something is not working properly
Comments
robertkirkman
added a commit
to robertkirkman/termux-packages
that referenced
this issue
Nov 16, 2024
…dless" Fixes termux#22286 Bypasses the unstable codepath by disabling `MOZ_HAS_REMOTE`, which does not seem to negatively affect the existing X11 behavior, only fixes the command `firefox -headless`; I am not 100% sure that someone else does not need that feature, but disabling it fixes `firefox -headless` and does not seem to break anything obvious that I have noticed from browsing with the X11 mode for a few minutes This patch is a dependency of my project, "How To Run Node.js Puppeteer On Android" https://gist.github.com/robertkirkman/0c2f3426024069546ed9b7bb2f26cb99. Which is a fully functional example of a Javascript program that invokes the system call `firefox -headless` through the Puppeteer library. I am hoping to possibly upstream the patch part of the necessary code for the headless mode on Termux of the Firefox backend of the Puppeteer Node.js library by submitting this PR.
robertkirkman
added a commit
to robertkirkman/termux-packages
that referenced
this issue
Nov 16, 2024
…dless" Fixes termux#22286 Bypasses the unstable codepath by disabling `MOZ_HAS_REMOTE`, which does not seem to negatively affect the existing X11 behavior, only fixes the command `firefox -headless`; I am not 100% sure that someone else does not need that feature, but disabling it fixes `firefox -headless` and does not seem to break anything obvious that I have noticed from browsing with the X11 mode for a few minutes
robertkirkman
added a commit
to robertkirkman/termux-packages
that referenced
this issue
Nov 17, 2024
…dless" Fixes termux#22286 Bypasses the unstable codepath by disabling `MOZ_HAS_REMOTE`, which does not seem to negatively affect the existing X11 behavior, only fixes the command `firefox -headless`; I am not 100% sure that someone else does not need that feature, but disabling it fixes `firefox -headless` and does not seem to break anything obvious that I have noticed from browsing with the X11 mode for a few minutes
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Problem description
The command
firefox -headlessdoes not work, which indirectly prevents the Node.js Puppeteer Core library that comes frompkg install nodejs && npm install puppeteer-corefrom working on Termux without having to also install Termux:X11, configure and launch Termux:X11, and configure Firefox for Termux:X11.Related issue in another repository that could also potentially be helped simultaneously by a solution to this issue: mermaid-js/mermaid-cli#777
If this is fixed then Puppeteer Core can work directly on Termux, in fully headless mode, without having to have any proot or X11, possibly presenting a viable alternative to the preexisting 3rd party solution that was available already, the proot-based method.
I believe the instances of "
Crash Annotation GraphicsCriticalError: |[0][GFX1-]: glxtest: Unable to open a connection to the X server (t=0.215055)" in the logs are probably extremely misleading red herrings, because they came from a different area of the code from where the backtrace leads, and after I fixed the crash, they still printed even while the program worked.backtrace
What steps will reproduce the bug?
What is the expected behavior?
(idles [desired behavior])
(This is an example of the output when it is actually working. Every error/warning in this section is spurious and was not related to the crash, and it works in spite of them)
System information
The text was updated successfully, but these errors were encountered: