I've also seen the problem like this, in fact it may be somewhat tricky sometimes to start chome at all. I've not reported since this is not desktop but server and chrome usage there is just exceptional case. If you are on desktop and you care about chrome health, it would be good if you obtain backtrace of the crash by installing egdb from ports and then egdb <which chrome> <chrome core file> -- on prompt do: bt and hit enter. And please send it here. Thanks!
On Thu, Oct 26, 2017 at 12:54 PM, Federico Giannici <giann...@neomedia.it> wrote: > Since I upgraded from OBSD 6.1 to 6.2 (amd64), at least half the time I > launch Chrome it crashes (with a "use after free"). > > Here is an example: > > casa:/home/giannici> chrome > [99256:2090071984:1026/093638.414135:ERROR:process_metrics_openbsd.cc(258)] > Not implemented reached in bool > base::GetSystemMemoryInfo(base::SystemMemoryInfoKB *) > [99256:2090071984:1026/093638.751329:ERROR:content_settings_pref.cc(448)] > Invalid pattern strings: ,https://www.agcom.it:443 > [99256:2090071984:1026/093638.751423:ERROR:content_settings_pref.cc(262)] > Invalid pattern strings: ,https://www.agcom.it:443 > [99256:637008952:1026/093638.808156:ERROR:object_proxy.cc(573)] Failed to > call method: org.kde.KWallet.isEnabled: object_path= /modules/kwalletd: > org.freedesktop.DBus.Error.ServiceUnknown: The name org.kde.kwalletd was not > provided by any .service files > [99256:637008952:1026/093638.808194:ERROR:kwallet_dbus.cc(100)] Error > contacting kwalletd (isEnabled) > [99256:637008952:1026/093639.121955:ERROR:object_proxy.cc(573)] Failed to > call method: org.kde.KWallet.isEnabled: object_path= /modules/kwalletd: > org.freedesktop.DBus.Error.NoReply: Message recipient disconnected from > message bus without replying > [99256:637008952:1026/093639.122087:ERROR:kwallet_dbus.cc(100)] Error > contacting kwalletd (isEnabled) > chrome(99256) in free(): use after free 0x1478a0f1fd00 > Abort (core dumped) > > Is this a problem specific to my installation (but it happens with my two > different PCs) or it's a common problem? > > Thanks. >
