SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
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.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
It works here, but I have certainly seen that behavior in the past. There are two bits in the SlackBuild to help prevent that problem - using -O1 as the optimization (more aggressive optimization seems to increase the odds of a crash), and -fno-delete-null-pointer-checks.
In case you were using a version of Seamonkey that was compiled with gcc-8.1.1, I recompiled it here. The resulting packages were still stable for me.
BTW, the site I use to test Seamonkey stability is onet.pl which was recommended to me by one of the people reporting Seamonkey crash issues. If that site won't crash it within 30 seconds, nothing will.
Seamonkey 2.49.3 (Slackware 14.2 latest update) does crash for me, occasionally. There might be a message but you have to look in your session log file or someplace like that. For me, the crash message always contains "ABORT: X_GLXDestroyContext: GLXBadContext". The crashes are not very frequent, and not repeatable, except for one particular web site I use, a mapping site hosted at arcgis.com, that always crashes Seamonkey when it first loads. (I use Firefox for that site...)
Distribution: slackware, slackware from scratch, LFS, slackware [arm], linux Mint...
Posts: 1,564
Original Poster
Rep:
I tested this:
- fresh install of slackware64 on a new partition: crash
- rebuild seamonkey with gcc-8.1.1 on my slackware64-current system: crash
- test on slackware-current (x86): crash
I tested this:
- fresh install of slackware64 on a new partition: crash
- rebuild seamonkey with gcc-8.1.1 on my slackware64-current system: crash
- test on slackware-current (x86): crash
Can you rebuild SeaMonkey in debug mode then run it with GDB (GNU Debugger)? Simply by running it in the debugger it should tell you more information why it crashes.
There is now a Slackware-14.2 update (patch) with Seamonkey 2.49.4.
This new Seamonkey is built with Gtk+3, where as previous Slackware versions were built with Gtk+2. It doesn't look very different to me, which is good. Other applications that moved from Gtk+2 to Gtk+3 got some weird features like auto-hiding scrollbars, which I don't like.
There was one website that Seamonkey-2.49.3 would always crash on for me, and the new 2.49.4 does NOT crash. That's very good news, although I just updated and haven't tested it that much.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.