Martijn Rijkeboer [mart...@bunix.org] wrote: > > I can't tell from your message whether this is the following problem: > > There is a diff being discussed that makes pledge "recvfd" stricter. It > > is plausible that Theo put this diff into the most recent snapshot. One > > result is that this diff will make chromium and iridium crash because > > they do not make "recvfd" promises. Do you see messages like > > > > chrome(99124): syscall 27 "recvfd" > > > > in your dmesg? > > > > If that's the case, chrome should still work with the old kernel or with > > a kernel compiled from source. > > Thanks for your response, this is indeed the problem. My dmesg is full of > "recvfd" en "stdio" pledge messages. >
This diff appears to be in -current now. You'll need to re build the chromium/iridium port.
