Dear Maintainer,

I have freshly installed Debian on a Raspberry Pi 3 with XFCE.
After starting firefox-esr it crashes instantly even when running in safe-mode or headless.
It produces the following error messages:

ExceptionHandler::GenerateDump cloned child 5256
ExceptionHandler::WaitForContinueSignal waiting for continue signal...
ExceptionHandler::SendContinueSignalToChild sent continue signal to child

The bug appears to be similar to #908396 (https://bugs.debian.org/908396),
which is reported to be closed.


Here is the backtrace:
Starting program: /usr/bin/firefox-esr
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/arm-linux-gnueabihf/libthread_db.so.1".
[New Thread 0x712ec450 (LWP 5352)]
[Thread 0x712ec450 (LWP 5352) exited]
[New Thread 0x712ec450 (LWP 5354)]
[New Thread 0x6d4ff450 (LWP 5355)]
[New Thread 0x6ccff450 (LWP 5356)]
[New Thread 0x6c4ff450 (LWP 5357)]
[New Thread 0x6bbff450 (LWP 5358)]
[New Thread 0x6b3ff450 (LWP 5359)]
[New Thread 0x6b1ff450 (LWP 5360)]
[New Thread 0x6afff450 (LWP 5361)]
[New Thread 0x6adff450 (LWP 5362)]
[New Thread 0x6a6ff450 (LWP 5363)]
[New Thread 0x6a4ff450 (LWP 5364)]
[New Thread 0x6a2ff450 (LWP 5365)]
[New Thread 0x69aff450 (LWP 5366)]
[New Thread 0x6926d450 (LWP 5374)]
[New Thread 0x68a6d450 (LWP 5375)]
[New Thread 0x67fff450 (LWP 5376)]
[New Thread 0x6826d450 (LWP 5378)]
[New Thread 0x677ff450 (LWP 5379)]

Thread 1 "firefox-esr" received signal SIGSEGV, Segmentation fault.


0x73a22aba in ?? () from /usr/lib/firefox-esr/libxul.so
#0  0x73a22aba in ?? () from /usr/lib/firefox-esr/libxul.so
No symbol table info available.
#1  0x73a22a8e in ?? () from /usr/lib/firefox-esr/libxul.so
No symbol table info available.
Backtrace stopped: previous frame identical to this frame (corrupt stack?)

I can reproduce this with firefox-esr 60.5 on a Cubieboard 2 running Stretch/armhf. However, in a Buster/armhf chroot Firefox works fine.

To make sure this is not a chroot effect I tried again in a Stretch/armhf chroot and it shows the same error as the Stetch/armhf host.
For sake of completeness I repeated the same in Stretch and Buster/armel chroots and got the same results as in the respective armhf counterparts.

So I'd conclude this problem is specific to the Stretch/arm* architectures.

Thanks. This bug looks like #909498. That was also reported on Stretch with a
Raspberry Pi. Can you still reproduce it?

Also look at #949834, but both individuals reported that from Bullseye or
unstable.

I'm sorry, but my Cubieboard is currently at my workplace, to which I have no access. I'll try to get clearance to pick it up, but I can't promise if or when that will be possible.

no access. I'll try to get clearance to pick it up, but I can't promise if or
when that will be possible.

It's not urgent, I wanted to ensure that you aren't having this issue anymore.
Sorry if it was unclear, I'm not a Firefox maintainer and wouldn't have any
clue how to fix this except for bringing it to Mozilla's attention.

Take care.

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?
   * What exactly did you do (or not do) that was effective (or
     ineffective)?
   * What was the outcome of this action?
   * What outcome did you expect instead?

*** End of the template - remove these template lines ***

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?
   * What exactly did you do (or not do) that was effective (or
     ineffective)?
   * What was the outcome of this action?
   * What outcome did you expect instead?

*** End of the template - remove these template lines ***

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?
   * What exactly did you do (or not do) that was effective (or
     ineffective)?
   * What was the outcome of this action?
   * What outcome did you expect instead?

*** End of the template - remove these template lines ***

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?
   * What exactly did you do (or not do) that was effective (or
     ineffective)?
   * What was the outcome of this action?
   * What outcome did you expect instead?

*** End of the template - remove these template lines ***

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?
   * What exactly did you do (or not do) that was effective (or
     ineffective)?
   * What was the outcome of this action?
   * What outcome did you expect instead?

*** End of the template - remove these template lines ***

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?
   * What exactly did you do (or not do) that was effective (or
     ineffective)?
   * What was the outcome of this action?
   * What outcome did you expect instead?

*** End of the template - remove these template lines ***