LIBGL_ALWAYS_SOFTWARE=true might let you test without access to unaccel'd
hardware.
If it is the same old problem then AFAIK the options are disable pledge,
patch X, or change how Firefox's multi process model works.
--
Sent from a phone, apologies for poor formatting.
On 12 April 2023
Le Wed, Apr 12, 2023 at 11:11:01AM +0200, Jan Stary a écrit :
> This is current/arm64 on an Apple M1 MacBook Air (dmesg below).
> While everything mostly works, Firefox keeps crashing.
>
> Reproducibly, it always crashes on calendar.google.com;
> _sometimes_ it crashes when playing a video.
> On
On 12/04/23 10:27 +0100, Stuart Henderson wrote:
> On 2023/04/12 11:15, Jan Stary wrote:
> > On Apr 12 11:11:01, h...@stare.cz wrote:
> > > This is current/arm64 on an Apple M1 MacBook Air (dmesg below).
> > > While everything mostly works, Firefox keeps crashing.
> > >
> > > Reproducibly, it
On 2023/04/12 11:15, Jan Stary wrote:
> On Apr 12 11:11:01, h...@stare.cz wrote:
> > This is current/arm64 on an Apple M1 MacBook Air (dmesg below).
> > While everything mostly works, Firefox keeps crashing.
> >
> > Reproducibly, it always crashes on calendar.google.com;
> > _sometimes_ it
On Apr 12 11:11:01, h...@stare.cz wrote:
> This is current/arm64 on an Apple M1 MacBook Air (dmesg below).
> While everything mostly works, Firefox keeps crashing.
>
> Reproducibly, it always crashes on calendar.google.com;
> _sometimes_ it crashes when playing a video.
> On simple sites, it
This is current/arm64 on an Apple M1 MacBook Air (dmesg below).
While everything mostly works, Firefox keeps crashing.
Reproducibly, it always crashes on calendar.google.com;
_sometimes_ it crashes when playing a video.
On simple sites, it works withotu problems.
How can I debug this? Is it
