Ryan Freeman [2019-03-17, 14:09:08]: > On Fri, Mar 15, 2019 at 07:52:50PM +0000, Bryan Everly wrote: > > Hi Ports@, > > > > Below is the terminal output I get when I try to launch the chromium build > > (latest & greatest package from snapshots) on the latest snapshot: > > > > $ chrome > > [40668:1870462320:0315/155107.446613:ERROR:process_metrics_openbsd.cc(126)] > > Not implemented reached in bool > > base::GetSystemMemoryInfo(base::SystemMemoryInfoKB *) > > [40668:1870462320:0315/155107.464615:ERROR:process_posix.cc(388)] Not > > implemented reached in base::Time base::Process::CreationTime() const > > Abort trap (core dumped) > > > > Any suggestions? > > > > Thanks! > > I still haven't been able to figure out what is causing this, my post here: > https://marc.info/?l=openbsd-ports&m=155181090804746&w=2
In your dmesg: chrome[55191]: pledge "", syscall 203 I see similar behavior with chrome (amd64), where pledge does not permit the mlock syscall, and the program is aborted. I use xenodm with xfce. If I run chrome as a different user than the one logged into xenodm, it works fine. I've also tried it with a clean profile, makes no difference. This started to happen +/- end of January.
