LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Slackware (https://www.linuxquestions.org/questions/slackware-14/)
-   -   seamonkey segfaults (https://www.linuxquestions.org/questions/slackware-14/seamonkey-segfaults-4175632942/)

nobodino 06-29-2018 09:21 AM

seamonkey segfaults
 
am I the only one for which seamonkey segfaults without any other message?

hitest 06-29-2018 09:28 AM

I'm running slackware64-current. I just launched seamonkey, it ran as expected.

rmartins 06-29-2018 01:09 PM

Seamonkey running OK here on current as well.

volkerdi 06-29-2018 01:41 PM

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.

nobodino 06-29-2018 02:29 PM

It's the official version, not the one I compiled in SFS.

ljb643 06-29-2018 09:30 PM

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...)

nobodino 06-30-2018 07:10 AM

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

the_pooch 07-06-2018 10:04 AM

Quote:

Originally Posted by nobodino (Post 5873898)
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.

Here's a quick GDB tutorial in case you need it:
http://unknownroad.com/rtfm/gdbtut/gdbtoc.html

nobodino 07-07-2018 05:54 AM

rebuilt on Slackware From Scratch it works, but not on my current systems.

ljb643 07-31-2018 04:15 PM

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.

elcore 08-01-2018 02:21 PM

Should've read that post before I wasted bandwidth on useless package. Anyway, thanks for letting us know.

nobodino 08-07-2018 05:26 AM

Finally I got it working by removing under ./mozilla directory the sub-directory seamonkey.


All times are GMT -5. The time now is 08:53 AM.