Re: firefox - some pages cause SIGILL
On 2024/01/25 16:40, Landry Breuil wrote: > Le Thu, Jan 25, 2024 at 04:17:18PM +0100, Simon a écrit : > > Hello Landry, > > > > Same Problem exist on AMD64, using 7.4 current #1623 at the moment. > > Firefox Version 121.0.1 > > But I don't have any more knowledge to give you more Information. > > since i dont have issues with 122.0 and 123.0b1 & 123.0b2, i'd guess > this is probably some desynch between the base snapshot and pkg > snapshot.. > > Landry > No issues with those sites here on 121.0.1 amd64 FWIW.
Re: firefox - some pages cause SIGILL
Le Thu, Jan 25, 2024 at 04:17:18PM +0100, Simon a écrit : > Hello Landry, > > Same Problem exist on AMD64, using 7.4 current #1623 at the moment. > Firefox Version 121.0.1 > But I don't have any more knowledge to give you more Information. since i dont have issues with 122.0 and 123.0b1 & 123.0b2, i'd guess this is probably some desynch between the base snapshot and pkg snapshot.. Landry
Re: firefox - some pages cause SIGILL
Hello Landry, Same Problem exist on AMD64, using 7.4 current #1623 at the moment. Firefox Version 121.0.1 But I don't have any more knowledge to give you more Information. Many Thanks for your awesome work. Best Regards Simon On 25 January 2024 15:35:06 CET, Landry Breuil wrote: >Le Wed, Jan 24, 2024 at 08:49:27AM +0100, Jan Stary a écrit : >> This is current/arm64 on a MacBook Air (M1), >> running the latest Firefox 121.0.1 >> >> Some webpages, such as reuters.com or theguardian.com, >> result in a tab crash, with firefix saying >> >> [Parent 94040, IPC I/O Parent] WARNING: process 47036 exited on signal 4: >> file >> /usr/obj/ports/firefox-121.0.1/firefox-121.0.1/ipc/chromium/src/base/process_util_posix.cc:315 >> >> [Parent 94040, IPC I/O Parent] WARNING: process 82372 exited on signal 4: >> file >> /usr/obj/ports/firefox-121.0.1/firefox-121.0.1/ipc/chromium/src/base/process_util_posix.cc:315 >> >> Other pages work just fine. >> >> Once the crash happens, ktrace -p $FOXPID -di -ts >> starts reporting a flood of these (full log below): >> >> 65273 firefox PSIG SIGSEGV caught handler=0x206f4b242c mask=0<> >> code=SEGV_ACCERR addr=0x206ac1630e trapno=-1845493745 >> 65273 firefox PSIG SIGSEGV caught handler=0x206f4b242c mask=0<> >> code=SEGV_ACCERR addr=0x206ac1630e trapno=-1845493745 >> 65273 firefox PSIG SIGSEGV caught handler=0x206f4b242c mask=0<> >> code=SEGV_ACCERR addr=0x206ac16fc8 trapno=-1845493745 >> 65273 firefox PSIG SIGSEGV caught handler=0x206f4b242c mask=0<> >> code=SEGV_MAPERR addr=0x0 trapno=-2113929211 >> 65273 firefox PSIG SIGSEGV caught handler=0x206f4b242c mask=0<> >> code=SEGV_MAPERR addr=0x0 trapno=-2113929211 >> 65273 firefox PSIG SIGSEGV caught handler=0x206f4b242c mask=0<> >> code=SEGV_MAPERR addr=0x0 trapno=-2113929211 >> 65273 firefox PSIG SIGSEGV caught handler=0x206f4b242c mask=0<> >> code=SEGV_MAPERR addr=0x0 trapno=-2113929211 >> 65273 firefox PSIG SIGSEGV caught handler=0x206f4b242c mask=0<> >> code=SEGV_MAPERR addr=0x0 trapno=-2113929211 >> 65273 firefox PSIG SIGSEGV caught handler=0x206f4b242c mask=0<> >> code=SEGV_MAPERR addr=0x0 trapno=-2113929211 >> 65273 firefox PSIG SIGSEGV caught handler=0x206f4b242c mask=0<> >> code=SEGV_MAPERR addr=0x0 trapno=-2113929211 >> 65273 firefox PSIG SIGSEGV caught handler=0x206f4b242c mask=0<> >> code=SEGV_MAPERR addr=0x0 trapno=-2113929211 >> 65273 firefox PSIG SIGSEGV caught handler=0x206f4b242c mask=0<> >> code=SEGV_MAPERR addr=0x0 trapno=-2113929211 >> 65273 firefox PSIG SIGSEGV caught handler=0x206f4b242c mask=0<> >> code=SEGV_MAPERR addr=0x0 trapno=-2113929211 >> 65273 firefox PSIG SIGSEGV caught handler=0x206f4b242c mask=0<> >> code=SEGV_MAPERR addr=0x0 trapno=-2113929211 >> 65273 firefox PSIG SIGSEGV caught handler=0x206f4b242c mask=0<> >> code=SEGV_MAPERR addr=0x0 trapno=-2113929211 >> 65273 firefox PSIG SIGSEGV caught handler=0x206f4b242c mask=0<> >> code=SEGV_MAPERR addr=0x0 trapno=-2113929211 >> 65273 firefox PSIG SIGSEGV caught handler=0x206f4b242c mask=0<> >> code=SEGV_ACCERR addr=0x206ac1630c trapno=-1845493745 >> 65273 firefox PSIG SIGSEGV caught handler=0x206f4b242c mask=0<> >> code=SEGV_MAPERR addr=0x0 trapno=-2113929211 >> 65273 firefox PSIG SIGSEGV caught handler=0x206f4b242c mask=0<> >> code=SEGV_ACCERR addr=0x206ac1630c trapno=-1845493745 >> 65273 firefox PSIG SIGSEGV caught handler=0x206f4b242c mask=0<> >> code=SEGV_MAPERR addr=0x0 trapno=-2113929211 >> >> Any idea what this is? >> How do I debug that? > >fwiw: >- i dont have an arm64 so i've never tested firefox there >- if i had an arm64, i'm not sure i'll had time to actually test it there >- and even if so, i wouldnt have the arm64 specific knowledge to actually help > >besides that, ktrace and egdb are the tools... you should be able to >install the debug symbol package, and examine coredumps. > >Landry >
Re: firefox - some pages cause SIGILL
Le Wed, Jan 24, 2024 at 08:49:27AM +0100, Jan Stary a écrit : > This is current/arm64 on a MacBook Air (M1), > running the latest Firefox 121.0.1 > > Some webpages, such as reuters.com or theguardian.com, > result in a tab crash, with firefix saying > > [Parent 94040, IPC I/O Parent] WARNING: process 47036 exited on signal 4: > file > /usr/obj/ports/firefox-121.0.1/firefox-121.0.1/ipc/chromium/src/base/process_util_posix.cc:315 > > [Parent 94040, IPC I/O Parent] WARNING: process 82372 exited on signal 4: > file > /usr/obj/ports/firefox-121.0.1/firefox-121.0.1/ipc/chromium/src/base/process_util_posix.cc:315 > > Other pages work just fine. > > Once the crash happens, ktrace -p $FOXPID -di -ts > starts reporting a flood of these (full log below): > > 65273 firefox PSIG SIGSEGV caught handler=0x206f4b242c mask=0<> > code=SEGV_ACCERR addr=0x206ac1630e trapno=-1845493745 > 65273 firefox PSIG SIGSEGV caught handler=0x206f4b242c mask=0<> > code=SEGV_ACCERR addr=0x206ac1630e trapno=-1845493745 > 65273 firefox PSIG SIGSEGV caught handler=0x206f4b242c mask=0<> > code=SEGV_ACCERR addr=0x206ac16fc8 trapno=-1845493745 > 65273 firefox PSIG SIGSEGV caught handler=0x206f4b242c mask=0<> > code=SEGV_MAPERR addr=0x0 trapno=-2113929211 > 65273 firefox PSIG SIGSEGV caught handler=0x206f4b242c mask=0<> > code=SEGV_MAPERR addr=0x0 trapno=-2113929211 > 65273 firefox PSIG SIGSEGV caught handler=0x206f4b242c mask=0<> > code=SEGV_MAPERR addr=0x0 trapno=-2113929211 > 65273 firefox PSIG SIGSEGV caught handler=0x206f4b242c mask=0<> > code=SEGV_MAPERR addr=0x0 trapno=-2113929211 > 65273 firefox PSIG SIGSEGV caught handler=0x206f4b242c mask=0<> > code=SEGV_MAPERR addr=0x0 trapno=-2113929211 > 65273 firefox PSIG SIGSEGV caught handler=0x206f4b242c mask=0<> > code=SEGV_MAPERR addr=0x0 trapno=-2113929211 > 65273 firefox PSIG SIGSEGV caught handler=0x206f4b242c mask=0<> > code=SEGV_MAPERR addr=0x0 trapno=-2113929211 > 65273 firefox PSIG SIGSEGV caught handler=0x206f4b242c mask=0<> > code=SEGV_MAPERR addr=0x0 trapno=-2113929211 > 65273 firefox PSIG SIGSEGV caught handler=0x206f4b242c mask=0<> > code=SEGV_MAPERR addr=0x0 trapno=-2113929211 > 65273 firefox PSIG SIGSEGV caught handler=0x206f4b242c mask=0<> > code=SEGV_MAPERR addr=0x0 trapno=-2113929211 > 65273 firefox PSIG SIGSEGV caught handler=0x206f4b242c mask=0<> > code=SEGV_MAPERR addr=0x0 trapno=-2113929211 > 65273 firefox PSIG SIGSEGV caught handler=0x206f4b242c mask=0<> > code=SEGV_MAPERR addr=0x0 trapno=-2113929211 > 65273 firefox PSIG SIGSEGV caught handler=0x206f4b242c mask=0<> > code=SEGV_MAPERR addr=0x0 trapno=-2113929211 > 65273 firefox PSIG SIGSEGV caught handler=0x206f4b242c mask=0<> > code=SEGV_ACCERR addr=0x206ac1630c trapno=-1845493745 > 65273 firefox PSIG SIGSEGV caught handler=0x206f4b242c mask=0<> > code=SEGV_MAPERR addr=0x0 trapno=-2113929211 > 65273 firefox PSIG SIGSEGV caught handler=0x206f4b242c mask=0<> > code=SEGV_ACCERR addr=0x206ac1630c trapno=-1845493745 > 65273 firefox PSIG SIGSEGV caught handler=0x206f4b242c mask=0<> > code=SEGV_MAPERR addr=0x0 trapno=-2113929211 > > Any idea what this is? > How do I debug that? fwiw: - i dont have an arm64 so i've never tested firefox there - if i had an arm64, i'm not sure i'll had time to actually test it there - and even if so, i wouldnt have the arm64 specific knowledge to actually help besides that, ktrace and egdb are the tools... you should be able to install the debug symbol package, and examine coredumps. Landry
Re: firefox - some pages cause SIGILL
On Jan 24 09:41:52, tobias.hei...@stusta.de wrote: > > > On January 24, 2024 8:49:27 AM GMT+01:00, Jan Stary wrote: > >This is current/arm64 on a MacBook Air (M1), > >running the latest Firefox 121.0.1 > > > >Some webpages, such as reuters.com or theguardian.com, > >result in a tab crash, with firefix saying > > > >[Parent 94040, IPC I/O Parent] WARNING: process 47036 exited on signal 4: > >file > >/usr/obj/ports/firefox-121.0.1/firefox-121.0.1/ipc/chromium/src/base/process_util_posix.cc:315 > > > >[Parent 94040, IPC I/O Parent] WARNING: process 82372 exited on signal 4: > >file > >/usr/obj/ports/firefox-121.0.1/firefox-121.0.1/ipc/chromium/src/base/process_util_posix.cc:315 > > > >Other pages work just fine. > > > >Once the crash happens, ktrace -p $FOXPID -di -ts > >starts reporting a flood of these (full log below): > > > > 65273 firefox PSIG SIGSEGV caught handler=0x206f4b242c mask=0<> > > code=SEGV_ACCERR addr=0x206ac1630e trapno=-1845493745 > > 65273 firefox PSIG SIGSEGV caught handler=0x206f4b242c mask=0<> > > code=SEGV_ACCERR addr=0x206ac1630e trapno=-1845493745 > > 65273 firefox PSIG SIGSEGV caught handler=0x206f4b242c mask=0<> > > code=SEGV_ACCERR addr=0x206ac16fc8 trapno=-1845493745 > > 65273 firefox PSIG SIGSEGV caught handler=0x206f4b242c mask=0<> > > code=SEGV_MAPERR addr=0x0 trapno=-2113929211 > > 65273 firefox PSIG SIGSEGV caught handler=0x206f4b242c mask=0<> > > code=SEGV_MAPERR addr=0x0 trapno=-2113929211 > > 65273 firefox PSIG SIGSEGV caught handler=0x206f4b242c mask=0<> > > code=SEGV_MAPERR addr=0x0 trapno=-2113929211 > > 65273 firefox PSIG SIGSEGV caught handler=0x206f4b242c mask=0<> > > code=SEGV_MAPERR addr=0x0 trapno=-2113929211 > > 65273 firefox PSIG SIGSEGV caught handler=0x206f4b242c mask=0<> > > code=SEGV_MAPERR addr=0x0 trapno=-2113929211 > > 65273 firefox PSIG SIGSEGV caught handler=0x206f4b242c mask=0<> > > code=SEGV_MAPERR addr=0x0 trapno=-2113929211 > > 65273 firefox PSIG SIGSEGV caught handler=0x206f4b242c mask=0<> > > code=SEGV_MAPERR addr=0x0 trapno=-2113929211 > > 65273 firefox PSIG SIGSEGV caught handler=0x206f4b242c mask=0<> > > code=SEGV_MAPERR addr=0x0 trapno=-2113929211 > > 65273 firefox PSIG SIGSEGV caught handler=0x206f4b242c mask=0<> > > code=SEGV_MAPERR addr=0x0 trapno=-2113929211 > > 65273 firefox PSIG SIGSEGV caught handler=0x206f4b242c mask=0<> > > code=SEGV_MAPERR addr=0x0 trapno=-2113929211 > > 65273 firefox PSIG SIGSEGV caught handler=0x206f4b242c mask=0<> > > code=SEGV_MAPERR addr=0x0 trapno=-2113929211 > > 65273 firefox PSIG SIGSEGV caught handler=0x206f4b242c mask=0<> > > code=SEGV_MAPERR addr=0x0 trapno=-2113929211 > > 65273 firefox PSIG SIGSEGV caught handler=0x206f4b242c mask=0<> > > code=SEGV_MAPERR addr=0x0 trapno=-2113929211 > > 65273 firefox PSIG SIGSEGV caught handler=0x206f4b242c mask=0<> > > code=SEGV_ACCERR addr=0x206ac1630c trapno=-1845493745 > > 65273 firefox PSIG SIGSEGV caught handler=0x206f4b242c mask=0<> > > code=SEGV_MAPERR addr=0x0 trapno=-2113929211 > > 65273 firefox PSIG SIGSEGV caught handler=0x206f4b242c mask=0<> > > code=SEGV_ACCERR addr=0x206ac1630c trapno=-1845493745 > > 65273 firefox PSIG SIGSEGV caught handler=0x206f4b242c mask=0<> > > code=SEGV_MAPERR addr=0x0 trapno=-2113929211 > > > >Any idea what this is? > >How do I debug that? > > might be a pledge violation. > check dmesg to see if there are any pledge errors. There are not; I would have said. > firefox sometimes tries to use shared memory when using software rendering. This is an arm64/current on an M1 macbook air which indeed does not have hardware acceleration; and the same crashes do not happen on amd64. But these are not the shmget pledge violation from earlier, at least dmesg does not mention any. Jan > > 65273 firefox PSIG SIGSEGV caught handler=0x206f4b242c mask=0<> > > code=SEGV_ACCERR addr=0x206ac1630e trapno=-1845493745 > > 65273 firefox PSIG SIGSEGV caught handler=0x206f4b242c mask=0<> > > code=SEGV_ACCERR addr=0x206ac1630e trapno=-1845493745 > > 65273 firefox PSIG SIGSEGV caught handler=0x206f4b242c mask=0<> > > code=SEGV_ACCERR addr=0x206ac16fc8 trapno=-1845493745 > > 65273 firefox PSIG SIGSEGV caught handler=0x206f4b242c mask=0<> > > code=SEGV_MAPERR addr=0x0 trapno=-2113929211 > > 65273 firefox PSIG SIGSEGV caught handler=0x206f4b242c mask=0<> > > code=SEGV_MAPERR addr=0x0 trapno=-2113929211 > > 65273 firefox PSIG SIGSEGV caught handler=0x206f4b242c mask=0<> > > code=SEGV_MAPERR addr=0x0 trapno=-2113929211 > > 65273 firefox PSIG SIGSEGV caught handler=0x206f4b242c mask=0<> > > code=SEGV_MAPERR addr=0x0 trapno=-2113929211 > > 65273 firefox PSIG SIGSEGV caught handler=0x206f4b242c mask=0<> > > code=SEGV_MAPERR addr=0x0 trapno=-2113929211 > > 65273 firefox PSIG SIGSEGV caught handler=0x206f4b242c mask=0<> > > code=SEGV_MAPERR addr=0x0 trapno=-2113929211 > > 65273 firefox PSIG SIGSEGV caught handler=0x206f4b242c mask=0<> > > code=SEGV_MAPERR add
Re: firefox - some pages cause SIGILL
On January 24, 2024 8:49:27 AM GMT+01:00, Jan Stary wrote: >This is current/arm64 on a MacBook Air (M1), >running the latest Firefox 121.0.1 > >Some webpages, such as reuters.com or theguardian.com, >result in a tab crash, with firefix saying > >[Parent 94040, IPC I/O Parent] WARNING: process 47036 exited on signal 4: file >/usr/obj/ports/firefox-121.0.1/firefox-121.0.1/ipc/chromium/src/base/process_util_posix.cc:315 > >[Parent 94040, IPC I/O Parent] WARNING: process 82372 exited on signal 4: file >/usr/obj/ports/firefox-121.0.1/firefox-121.0.1/ipc/chromium/src/base/process_util_posix.cc:315 > >Other pages work just fine. > >Once the crash happens, ktrace -p $FOXPID -di -ts >starts reporting a flood of these (full log below): > > 65273 firefox PSIG SIGSEGV caught handler=0x206f4b242c mask=0<> > code=SEGV_ACCERR addr=0x206ac1630e trapno=-1845493745 > 65273 firefox PSIG SIGSEGV caught handler=0x206f4b242c mask=0<> > code=SEGV_ACCERR addr=0x206ac1630e trapno=-1845493745 > 65273 firefox PSIG SIGSEGV caught handler=0x206f4b242c mask=0<> > code=SEGV_ACCERR addr=0x206ac16fc8 trapno=-1845493745 > 65273 firefox PSIG SIGSEGV caught handler=0x206f4b242c mask=0<> > code=SEGV_MAPERR addr=0x0 trapno=-2113929211 > 65273 firefox PSIG SIGSEGV caught handler=0x206f4b242c mask=0<> > code=SEGV_MAPERR addr=0x0 trapno=-2113929211 > 65273 firefox PSIG SIGSEGV caught handler=0x206f4b242c mask=0<> > code=SEGV_MAPERR addr=0x0 trapno=-2113929211 > 65273 firefox PSIG SIGSEGV caught handler=0x206f4b242c mask=0<> > code=SEGV_MAPERR addr=0x0 trapno=-2113929211 > 65273 firefox PSIG SIGSEGV caught handler=0x206f4b242c mask=0<> > code=SEGV_MAPERR addr=0x0 trapno=-2113929211 > 65273 firefox PSIG SIGSEGV caught handler=0x206f4b242c mask=0<> > code=SEGV_MAPERR addr=0x0 trapno=-2113929211 > 65273 firefox PSIG SIGSEGV caught handler=0x206f4b242c mask=0<> > code=SEGV_MAPERR addr=0x0 trapno=-2113929211 > 65273 firefox PSIG SIGSEGV caught handler=0x206f4b242c mask=0<> > code=SEGV_MAPERR addr=0x0 trapno=-2113929211 > 65273 firefox PSIG SIGSEGV caught handler=0x206f4b242c mask=0<> > code=SEGV_MAPERR addr=0x0 trapno=-2113929211 > 65273 firefox PSIG SIGSEGV caught handler=0x206f4b242c mask=0<> > code=SEGV_MAPERR addr=0x0 trapno=-2113929211 > 65273 firefox PSIG SIGSEGV caught handler=0x206f4b242c mask=0<> > code=SEGV_MAPERR addr=0x0 trapno=-2113929211 > 65273 firefox PSIG SIGSEGV caught handler=0x206f4b242c mask=0<> > code=SEGV_MAPERR addr=0x0 trapno=-2113929211 > 65273 firefox PSIG SIGSEGV caught handler=0x206f4b242c mask=0<> > code=SEGV_MAPERR addr=0x0 trapno=-2113929211 > 65273 firefox PSIG SIGSEGV caught handler=0x206f4b242c mask=0<> > code=SEGV_ACCERR addr=0x206ac1630c trapno=-1845493745 > 65273 firefox PSIG SIGSEGV caught handler=0x206f4b242c mask=0<> > code=SEGV_MAPERR addr=0x0 trapno=-2113929211 > 65273 firefox PSIG SIGSEGV caught handler=0x206f4b242c mask=0<> > code=SEGV_ACCERR addr=0x206ac1630c trapno=-1845493745 > 65273 firefox PSIG SIGSEGV caught handler=0x206f4b242c mask=0<> > code=SEGV_MAPERR addr=0x0 trapno=-2113929211 > >Any idea what this is? >How do I debug that? might be a pledge violation. check dmesg to see if there are any pledge errors. firefox sometimes tries to use shared memory when using software rendering. > > Jan > > > 65273 firefox PSIG SIGSEGV caught handler=0x206f4b242c mask=0<> > code=SEGV_ACCERR addr=0x206ac1630e trapno=-1845493745 > 65273 firefox PSIG SIGSEGV caught handler=0x206f4b242c mask=0<> > code=SEGV_ACCERR addr=0x206ac1630e trapno=-1845493745 > 65273 firefox PSIG SIGSEGV caught handler=0x206f4b242c mask=0<> > code=SEGV_ACCERR addr=0x206ac16fc8 trapno=-1845493745 > 65273 firefox PSIG SIGSEGV caught handler=0x206f4b242c mask=0<> > code=SEGV_MAPERR addr=0x0 trapno=-2113929211 > 65273 firefox PSIG SIGSEGV caught handler=0x206f4b242c mask=0<> > code=SEGV_MAPERR addr=0x0 trapno=-2113929211 > 65273 firefox PSIG SIGSEGV caught handler=0x206f4b242c mask=0<> > code=SEGV_MAPERR addr=0x0 trapno=-2113929211 > 65273 firefox PSIG SIGSEGV caught handler=0x206f4b242c mask=0<> > code=SEGV_MAPERR addr=0x0 trapno=-2113929211 > 65273 firefox PSIG SIGSEGV caught handler=0x206f4b242c mask=0<> > code=SEGV_MAPERR addr=0x0 trapno=-2113929211 > 65273 firefox PSIG SIGSEGV caught handler=0x206f4b242c mask=0<> > code=SEGV_MAPERR addr=0x0 trapno=-2113929211 > 65273 firefox PSIG SIGSEGV caught handler=0x206f4b242c mask=0<> > code=SEGV_MAPERR addr=0x0 trapno=-2113929211 > 65273 firefox PSIG SIGSEGV caught handler=0x206f4b242c mask=0<> > code=SEGV_MAPERR addr=0x0 trapno=-2113929211 > 65273 firefox PSIG SIGSEGV caught handler=0x206f4b242c mask=0<> > code=SEGV_MAPERR addr=0x0 trapno=-2113929211 > 65273 firefox PSIG SIGSEGV caught handler=0x206f4b242c mask=0<> > code=SEGV_MAPERR addr=0x0 trapno=-2113929211 > 65273 firefox PSIG SIGSEGV caught handler=0x206f4b242c mask=0<> > code=SEGV_MAPERR addr=0x0 trapno=-2113929211 > 65273 firefo
