SlackwareThis Forum is for the discussion of Slackware Linux.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
Its not crashing for me in Current and I use it all the time. Perhaps an add-on/plugin is affecting it (looks over at Shockwave Flash). I use lightbeam, openh264, ant video, and Firefox hasn't crashed on me once.
firefox 52.x has Electrolysis enabled by default, which is a huge improvement, but not all the addons works fine and some even disable it, go to "about:support" in the address bar (check for "multi process") and see
Could be a problem with new requirements that v52 introduced, like for example gstreamer flag that was noted in old 14.1 slackbuild has been deprecated.
From what I've seen gstreamer is now irrelevant, latest version needs parts of ffmpeg, specifically the libvpx part.
It's possible some sites have embedded media which cause the crash in case ffmpeg is missing or compiled without required media library.
Note that I don't use 14.1 or firefox, but I've built icecat v52 (which is based on firefox v52) on slackware64-14.2 and linked it with ffmpeg-3.2.4 libvpx-1.6.1 and gtk+2-2.24.31 with no problem, it hasn't crashed yet.
Other than that, I don't know why it would crash, could be anything, even python or automake version mismatch, it's not like it hasn't happened before.
..strongly suggest to revert to 45 ESR until this is sorted out
Thank you Niki is very sound advice..
However when you say-
I get crash reports galore on all machines for Firefox
Can you detect any kinda pattern or similarities in the type of errors causing the crashes?
I'm trying to approach this as a opportunity for me to learn (slowly) some basic application debugging. I am hoping there are individuals on this board that can provide me with some basic guidance on HOW TO narrow down the actual cause of the crashes.
Why is it occurring here and not here?
Meaning what is the most likely error causing slice of code (or even just general section of code) that is different on this page that is NOT on that page.
Does anyone here know WHERE the crash error logs can be found on a slackware machine?
Nothing shows up in:
I understand mozzilla firefox provides the about:crashes screen within the browser itself but nothing is appearing for me there. I imagine the Operating System MUST log an error someplace BEFORE it appears to the Browser API. Does anyone on this board now where I should first look for it?
By launching firefox from within the terminal window:
I understand segmentation faults CAN be caused by failing RAM chips.. So i ran memtest+ for three passes with no errors and was hoping someone else could corroborate the same crash using the same:
System 14.1 32bit
Software version from official repository mozilla-firefox-52.0.2esr-i486-2_slack14.1.txz and
"There are four common mistakes that lead to segmentation faults: dereferencing NULL, dereferencing an uninitialized pointer, dereferencing a pointer that has been freed (or deleted, in C++) or that has gone out of scope (in the case of arrays declared in functions), and writing off the end of an array. " Source:http://www.cprogramming.com/debugging/segfaults.html
It would be FUN to find where exactly this is occurring or even just to eliminate where it is NOT occurring. But my debugging knowledge is pretty slim.
If you want to debug it, build firefox with debugging symbols, run it in gdb, reproduce the crash, get a backtrace and finally share it with the firefox devs.
Sorry, but I don't have time to potty-train the new Firefox version. I'll see how I can get my hands on the previous 45.8.0 version (which unfortunately disappeared from all the Slackware mirrors) and install that while the Firefox devs get their act together.