Page 1 of 1

version 27.6.2-1 Crash on Archlinux

Posted: 2017-12-04, 04:41
by jerome
Installed from package AUR repo palemoon 27.6.2-1 version crash with error message from terminal emulator:
[1] 22597 segmentation fault (core dumped) palemoon
:crazy:

this archlinux OS is running on device i7 8 cores.
last update on the morning (and rebooted due to new kernel), linux kernel running is: 4.14.3-1-ARCH version
gcc-multilib and gcc-libs-multilib 7.2.0-3 (i need the multilib version)
gcc6 and gcc6-libs version 6.4.1-4 installed also
lib32-gcc-libs 7.2.0-3 installed


strace palemoon :
:coffee:
https://ptpb.pw/A2MR

i would be happy to try and see palemoon working (i have to post the same kind of bug report for basilisk web browser... who has same team dev. Same team dev... same result ? :D )

good luck and thank you for this web browser, the idea is a very good idea, hope you will find a solution soon. :clap:

Re: version 27.6.2-1 Crash on Archlinux

Posted: 2017-12-04, 17:48
by trava90
Please note that installing from the AUR is not recommended as most of the maintainers there refuse to use sane build configs. Which AUR package did you use?

Re: version 27.6.2-1 Crash on Archlinux

Posted: 2017-12-04, 20:11
by Walter Dnes
I agree with Trava90. Another issue is that "-fpie" in CFLAGS/CXXFLAGS is the new fad with GCC-6.4 and up. If you have a system that is partially "pie", and partially "not-pie" you will have problems. Ditto for "-fpic".

Meanwhile on the Gentoo mailing list, where we compile just about everything from source, someone wondered why the unofficial Pale Moon overly ebuild insisted on pulling in an older GCC. So he tweaked it to build with GCC 6.4, and got a crash-y Pale Moon. And nobody has succeeded yet in building Pale Moon with GCC 7.2. Gentoo is also in the middle of a profile conversion to having PIE on by default. This could be a fiasco.

I strongly suggest using the official build.

Re: version 27.6.2-1 Crash on Archlinux

Posted: 2017-12-07, 02:31
by jooch
Could be more to it than just installs from the AUR...

I'm experiencing the same issue on Manjaro with palemoon from the stable repositories and a clean profile, version 27.6.2-1 won't even run in safe mode. Downgrading to 27.5.1-1 allows me to run for a short time with a clean profile, but not my own profile (immediate crash). Also Fossamail (yes i still use it), ceased to work at the same time. Runs for a short period then crashes.

Re: version 27.6.2-1 Crash on Archlinux

Posted: 2017-12-07, 03:18
by Walter Dnes
More from the Gentoo mailing list, and (not) crashing with a GCC-6.4 Pale Moon build. There's a strange report that setting ulimit -c unlimited (which has to be done as root or sudo) allows the crash-y GCC-6.4 Pale Moon build to run OK. The user says that even a low value may be sufficient, as long as it's not the default zero. To quote all the "B grade" scifi movies... that does not compute. But itt may be worth a try.

Re: version 27.6.2-1 Crash on Archlinux

Posted: 2017-12-07, 05:04
by hobbledehoy899
trava90 wrote:Please note that installing from the AUR is not recommended as most of the maintainers there refuse to use sane build configs.
Off-topic:
Does this apply to the binary package as well?

Re: version 27.6.2-1 Crash on Archlinux

Posted: 2017-12-07, 13:13
by jooch
So i tested 27.6.2-1 today on my Manjaro laptop which is not updated, works fine. Maybe something else makes palemoon crash?

Re: version 27.6.2-1 Crash on Archlinux

Posted: 2017-12-07, 13:36
by trava90
hobbledehoy899 wrote:Does this apply to the binary package as well?
I just checked and it looks like this particular package simply downloads and extracts the tarball from linux.palemoon.org.

@jooch that sounds to me like something changed in your system that doesn't like Pale Moon or FossaMail. FTR I use both Pale Moon and FossaMail daily on my up-to-date Manjaro box and have not encountered any crashing issues.

Re: version 27.6.2-1 Crash on Archlinux

Posted: 2017-12-07, 17:28
by jooch
trava90 wrote: @jooch that sounds to me like something changed in your system that doesn't like Pale Moon or FossaMail. FTR I use both Pale Moon and FossaMail daily on my up-to-date Manjaro box and have not encountered any crashing issues.
Seems so, i can't think of anything else. This system is otherwise very stable, CPU or RAM tests can run for hours without errors.
I updated the laptop which is now running PM fine with all the updates. My laptop and desktop both use the same Nvidia driver and system kernel.
I´ll check if there are any package differences between the two.

Maybe this strace can give a hint?

Code: Select all

openat(AT_FDCWD, "/usr/lib/libevent-2.1.so.6", O_RDONLY|O_CLOEXEC) = 70
read(70, "\177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0\340\364\0\0\0\0\0\0"..., 832) = 832
fstat(70, {st_mode=S_IFREG|0755, st_size=349944, ...}) = 0
mmap(NULL, 2446920, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 70, 0) = 0x7f243e63d000
mprotect(0x7f243e691000, 2093056, PROT_NONE) = 0
mmap(0x7f243e890000, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 70, 0x53000) = 0x7f243e890000
mmap(0x7f243e892000, 1608, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x7f243e892000
close(70)                               = 0
openat(AT_FDCWD, "/usr/lib/libcrypto.so.1.1", O_RDONLY|O_CLOEXEC) = 70
read(70, "\177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0\0p\6\0\0\0\0\0"..., 832) = 832
fstat(70, {st_mode=S_IFREG|0755, st_size=2594952, ...}) = 0
mmap(NULL, 4704640, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 70, 0) = 0x7f243e1c0000
mprotect(0x7f243e413000, 2093056, PROT_NONE) = 0
mmap(0x7f243e612000, 163840, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 70, 0x252000) = 0x7f243e612000
mmap(0x7f243e63a000, 10624, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x7f243e63a000
close(70)                               = 0
openat(AT_FDCWD, "/usr/lib/libicuuc.so.59", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
munmap(0x7f2458d0a000, 274290)          = 0
munmap(0x7f243ede2000, 3264864)         = 0
munmap(0x7f243ea96000, 3456024)         = 0
munmap(0x7f243e893000, 2105552)         = 0
munmap(0x7f243e63d000, 2446920)         = 0
openat(AT_FDCWD, "/etc/ld.so.cache", O_RDONLY|O_CLOEXEC) = 70
fstat(70, {st_mode=S_IFREG|0644, st_size=274290, ...}) = 0
mmap(NULL, 274290, PROT_READ, MAP_PRIVATE, 70, 0) = 0x7f2458d0a000
close(70)                               = 0
openat(AT_FDCWD, "/usr/lib/libXt.so", O_RDONLY|O_CLOEXEC) = 70
read(70, "\177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0\200<\1\0\0\0\0\0"..., 832) = 832
fstat(70, {st_mode=S_IFREG|0755, st_size=426296, ...}) = 0
close(70)                               = 0
--- SIGSEGV {si_signo=SIGSEGV, si_code=SEGV_MAPERR, si_addr=0xc8} ---
unlink("/home/barry/.moonchild productions/pale moon/sfxly7b4.default/lock") = 0
close(10)                               = 0
rt_sigaction(SIGSEGV, {sa_handler=SIG_DFL, sa_mask=[], sa_flags=SA_RESTORER, sa_restorer=0x7f247a474da0}, NULL, 8) = 0
rt_sigprocmask(SIG_UNBLOCK, [SEGV], NULL, 8) = 0
rt_sigprocmask(SIG_BLOCK, ~[RTMIN RT_1], [], 8) = 0
getpid()                                = 3653
gettid()                                = 3653
tgkill(3653, 3653, SIGSEGV)             = 0
rt_sigprocmask(SIG_SETMASK, [], NULL, 8) = 0
--- SIGSEGV {si_signo=SIGSEGV, si_code=SI_TKILL, si_pid=3653, si_uid=1000} ---
+++ killed by SIGSEGV (core dumped) +++

Re: version 27.6.2-1 Crash on Archlinux

Posted: 2017-12-07, 17:46
by jooch
Got it. It was caused by flash crap again. In my case freshplayerplugin-git

@Jerome
Could you check for any flash stuff or other plugins?