Palemoon Segfault on Archlinux

Users and developers helping users with generic and technical Pale Moon issues on all operating systems.

Moderator: trava90

Forum rules
This board is for technical/general usage questions and troubleshooting for the Pale Moon browser only.
Technical issues and questions not related to the Pale Moon browser should be posted in other boards!
Please keep off-topic and general discussion out of this board, thank you!
JoshH100

Palemoon Segfault on Archlinux

Unread post by JoshH100 » 2018-04-24, 16:29

Palemoon will run for a few seconds and then segfaults.
I am using the palemoon-27.9.0.en-US.linux-x86_64.tar.bz2 binary build directly from the palemoon site. I have tried a few older versions and they also segfault. I think the last versions that worked were v26 or 27.

Using gdb to run palemoon shows:

Code: Select all

[New Thread 0x7fffd4096700 (LWP 20289)]
[New Thread 0x7fffd3895700 (LWP 20290)]
[New Thread 0x7fffd2cff700 (LWP 20291)]
[New Thread 0x7fffd22f4700 (LWP 20292)]
[New Thread 0x7fffd1af3700 (LWP 20293)]
[New Thread 0x7fffd12f2700 (LWP 20294)]
....(lots of new thread messages)....
Thread 1 "palemoon-bin" received signal SIGSEGV, Segmentation fault.
0x00007ffff7de3a48 in _dl_relocate_object () from /lib64/ld-linux-x86-64.so.2
....
Thread 1 "palemoon-bin" received signal SIGSEGV, Segmentation fault.
0x00007ffff7bcbc70 in raise () from /usr/lib/libpthread.so.0
ldd shows the following shared libraries:

Code: Select all

        linux-vdso.so.1 (0x00007ffda83cd000)                                                                                                                                                                                                                           
        libpthread.so.0 => /usr/lib/libpthread.so.0 (0x00007ff33e79e000)
        libdl.so.2 => /usr/lib/libdl.so.2 (0x00007ff33e59a000)
        libstdc++.so.6 => /usr/lib/libstdc++.so.6 (0x00007ff33e213000)
        libm.so.6 => /usr/lib/libm.so.6 (0x00007ff33dec7000)
        libc.so.6 => /usr/lib/libc.so.6 (0x00007ff33db10000)
        /lib64/ld-linux-x86-64.so.2 => /usr/lib64/ld-linux-x86-64.so.2 (0x00007ff33e9bc000)
        libgcc_s.so.1 => /usr/lib/libgcc_s.so.1 (0x00007ff33d8f9000)
This is on Archlinux, kernel version 4.15.15-1

User avatar
adesh
Board Warrior
Board Warrior
Posts: 1277
Joined: 2017-06-06, 07:38

Re: Palemoon Segfault on Archlinux

Unread post by adesh » 2018-04-24, 17:19

I use Arch Linux 32-bit and Pale Moon almost never crashed/segfault'ed in last one year. I haven't updated my system in quite a while, so I'm still on 4.14 kernel version. My version of Pale Moon is also a little older - 27.8.1; I'm not going to install anything until 28 comes out 8-) . I use Pale Moon exclusively and it has been very stable for me in everyday use.

JoshH100

Re: Palemoon Segfault on Archlinux

Unread post by JoshH100 » 2018-04-24, 17:50

adesh wrote:I use Arch Linux 32-bit and Pale Moon almost never crashed/segfault'ed in last one year. I haven't updated my system in quite a while, so I'm still on 4.14 kernel version. My version of Pale Moon is also a little older - 27.8.1; I'm not going to install anything until 28 comes out 8-) . I use Pale Moon exclusively and it has been very stable for me in everyday use.
I've have tried versions all the way back to 24.4 and I am still getting segfaults now so it is probably related to some other archlinux package update.

Artemis3

Re: Palemoon Segfault on Archlinux

Unread post by Artemis3 » 2018-05-13, 16:29

palemoon-bin 27.9.1-1 from aur is working perfectly fine here.

BenFenner
Astronaut
Astronaut
Posts: 588
Joined: 2015-06-01, 12:52
Location: US Southeast

Re: Palemoon Segfault on Archlinux

Unread post by BenFenner » 2018-05-15, 13:47

64-bit Pale Moon on Arch here and been running great for years. We setup a new co-worker with Pale Moon on Arch recently and that went fine too.
Sorry I can't be of more help.

JSkier

Re: Palemoon Segfault on Archlinux

Unread post by JSkier » 2018-05-23, 20:29

Same issues and gdb output for me as well. It's unusable. Bin or build from source (ArchLinux packages) both segfault. Tried with Intel, NVIDIA, and AMD gpus (all on x86_64).

User avatar
distantpluto
Fanatic
Fanatic
Posts: 115
Joined: 2015-12-17, 18:28
Location: UK

Re: Palemoon Segfault on Archlinux

Unread post by distantpluto » 2018-05-24, 10:42

This will be of no use to you but hey, just for comparison...

I've been building Pale Moon from the AUR package for a couple of years and never had a single segfault (that I can recall). The problem is, us Arch users have different installs. I don't use a DE for example, my window manager is Compiz (0.8). My kernel is always the latest, everything always bang up to date. i7 4790k, GTX 970 (nvidia 396.24-4).

Maybe the two of you having the segfaults have something in common in the way of installed software?
Pale Moon and Epyrus on Arch Linux.

User avatar
trava90
Contributing developer
Contributing developer
Posts: 1736
Joined: 2013-05-20, 18:19
Location: Somewhere in Sector 001

Re: Palemoon Segfault on Archlinux

Unread post by trava90 » 2018-05-24, 11:34

Have you tried the binaries from linux.palemoon.org?

Graith

Re: Palemoon Segfault on Archlinux

Unread post by Graith » 2018-05-27, 02:37

Having the same issues, using the binary version, and I have the same gdb output when it crashes.

My system is AMD and I'm using Cinnamon as my desktop manager.

Walter Dnes
Astronaut
Astronaut
Posts: 650
Joined: 2015-07-30, 20:29
Location: Vaughan, ON, Canada

Re: Palemoon Segfault on Archlinux

Unread post by Walter Dnes » 2018-05-27, 04:51

Graith wrote:My system is AMD and I'm using Cinnamon as my desktop manager.
Would that happen to be an AMD Ryzen? Google shows a lot of hits... https://www.google.com/search?ei=IjgKW4ToA4S0jwS3i42YDA&q=amd+crash+linux&oq=amd+crash+linux
There's a right way
There's a wrong way
And then there's my way

User avatar
Lunokhod
Lunatic
Lunatic
Posts: 469
Joined: 2017-04-20, 21:25
Contact:

Re: Palemoon Segfault on Archlinux

Unread post by Lunokhod » 2018-05-28, 03:22

Thread 1 "palemoon-bin" received signal SIGSEGV, Segmentation fault.
0x00007ffff7de3a48 in _dl_relocate_object () from /lib64/ld-linux-x86-64.so.2
....
Thread 1 "palemoon-bin" received signal SIGSEGV, Segmentation fault.
0x00007ffff7bcbc70 in raise () from /usr/lib/libpthread.so.0

Both these binarys are from glibc. _dl_relocate_object () seems to be a low level internal function related to memory relocation on the stack, involved in the dynamic loading of libraries from what I read. It could be being passed a wrong or null value for some unknown reason. There could be several possible things worth trying to change about if anyone wanted, like versions of kernel, microcode, glibc, possibly anything that could be loading a dynamic library that interfaces with Pale Moon, that is assuming that it used to work but now no longer does.
Wait, it's all Ohio? Always has been...

User avatar
trava90
Contributing developer
Contributing developer
Posts: 1736
Joined: 2013-05-20, 18:19
Location: Somewhere in Sector 001

Re: Palemoon Segfault on Archlinux

Unread post by trava90 » 2018-05-28, 13:09

Let me ask again, has anyone tried the binaries from linux.palemoon.org?

JSkier

Re: Palemoon Segfault on Archlinux

Unread post by JSkier » 2018-06-13, 14:37

Latest palemoon-bin seems fine.

@trava90, ArchLinux palemoon-bin package is the binary sourced directly from palemoon.org btw. To answer your question, yes, I have tried both compiling from source and the binaries.
Last edited by JSkier on 2018-06-13, 14:37, edited 1 time in total.

Locked