Re: firefox52 core dump on RPI2 NetBSD9.1

[Bodie <bodie%bodie.cz@localhost>]

On 19.11.2020 03:08, Mayuresh wrote:
> On Wed, Nov 18, 2020 at 08:32:42AM +0530, Mayuresh wrote:
> > Is nobody else facing this problem? The image and packages both are
> > downloaded from above locations, I have built nothing at my end.
>
> Have filed port-arm/55812. Request attention please. Stuck without a
> browser totally.

I have eg.

armv7$ firefox52
Assertion failure: !joinable(), at 
/scratch/work/www/firefox52/work/firefox-52.9.0esr/js/src/threading/Thread.h:122
Memory fault (core dumped)
armv7$

Core was generated by `firefox52'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  0x7af78c70 in _lwp_kill () from /usr/lib/libc.so.12
[Current thread is 1 (process 1)]
(gdb) where
#0  0x7af78c70 in _lwp_kill () from /usr/lib/libc.so.12
#1  0x7723ea08 in ?? () from /usr/pkg/lib/firefox52/libxul.so
#2  0x7af789f8 in __vfork14 () from /usr/lib/libc.so.12
Backtrace stopped: previous frame identical to this frame (corrupt 
stack?)
(gdb)

Based on discussion on other list you were given tips what to do,
did you test them?

Besides based on your description you picked up totally wrong platform
for your job. Raspberry Pi 2 is having maxium of 1GB RAM if it is B 
model.
Firefox needs at least 512MB 
https://www.mozilla.org/en-US/firefox/52.0esr/system-requirements/
But that is minimum. Modern overbloated web browsers like Firefox and 
Chrome
needs A LOT of memory just for regular tasks. Eg. Firefox 82 needs at 
least
2GB of RAM in case of 64bit platform, currently it eats about 1,6GB on 
my PC
with about 12 tabs open doing nothing, except of writing this email.
Even if you will get it running then you can't rely on it for some huge
tasks with JavaScript which adds even more misery in to this mix.

If this is Severity - critical for you and you are stuck without browser
completely then you did something seriously wrong in planning phase of
whatever project you're in, because it means you do not have backup
platform or better to say more suited platform for the task at hands ;-)

Sad status of web browsers on arm architecture is one of the results of
"funny" cycle 90's IE only -> 2000's different options available ->
Now's Linux/Chrome or die (MS Edge anynone? :-)); with Firefox still
catching up somewhat