Re: Chrome crashes with 6.2
> I've just tried Iridium, from UX it's basically Chromium from 6.1 - > The i386 package of Chrome on 6.1 was slow Folks, this is misc@ not ports@ or wishes@ !
Re: Chrome crashes with 6.2
Cág writes: > I've just tried Iridium, from UX it's basically Chromium from 6.1 - > gtk2, none of that dreadfull new design - whoever thought that it was a > good idea to add A LOT of space, make letters even smaller and of an > almost indistinguishable from the background colour for my half-blind > eyes. I'm running chromium-61.0.3163.100 from packages, OpenBSD 6.2 release amd64. No crashes, no issues. Allan
Re: Chrome crashes with 6.2
> Iridium is based on Chromium, isn't it slow on an i386 too? > I actually would rather see Pale Moon or GTK+2 Chromium (as a separate > package/flavour). I've just tried Iridium, from UX it's basically Chromium from 6.1 - gtk2, none of that dreadfull new design - whoever thought that it was a good idea to add A LOT of space, make letters even smaller and of an almost indistinguishable from the background colour for my half-blind eyes. -- caóc
Re: Chrome crashes with 6.2
On 10/27/17 17:58, Cág wrote: > Dumitru Mișu Moldovan wrote: > >> If anyone wonders if there's still a usable (possibly full-blown) >> browser for i386, I'm running SeaMonkey and Iridium (the latter for some >> web apps, such as Google Music). Firefox has got too bloated, >> especially since 52.x builds (starting with 6.1) use multiple processes >> and GTK+ 3.x. > > Iridium is based on Chromium, isn't it slow on an i386 too? > > I actually would rather see Pale Moon or GTK+2 Chromium (as a separate > package/flavour). The i386 package of Chrome on 6.1 was slow, but reliable (once you got it started, as it crashed often when launched, as referenced in this thread). On 6.2 (both x86 arches), Chrome is even slower (because of GTK+ 3.x, I suppose) and completely unusable for me on i386, as said. Iridium on 6.2, on both arches, seems to be on par with Chrome from 6.1 (it's also built against GTK 2.x and perhaps a couple of versions ahead of it). For what it's worth, this is a reverse of a trend, up to 6.1 Chrome was getting more and more usable with every release on i386 (I think I've started using it in 5.8). Not complaining, the writing is on the wall for this arch. Just trying to get what life is left in some old but still usable hardware, fighting consumerism along the way. signature.asc Description: OpenPGP digital signature
Re: Chrome crashes with 6.2
Dumitru Mișu Moldovan wrote: > If anyone wonders if there's still a usable (possibly full-blown) > browser for i386, I'm running SeaMonkey and Iridium (the latter for some > web apps, such as Google Music). Firefox has got too bloated, > especially since 52.x builds (starting with 6.1) use multiple processes > and GTK+ 3.x. Iridium is based on Chromium, isn't it slow on an i386 too? I actually would rather see Pale Moon or GTK+2 Chromium (as a separate package/flavour). -- caóc
Re: Chrome crashes with 6.2 (Please update official download sites!)
Federico Giannici wrote: > As this snapshot package will soon disappear for new ones with incompatible > dependences, I think that it would be VERY useful for A LOT of people that > this package be put in the official download sites. They would have to wait for 6.3 or follow -current. -- caóc
Re: Chrome crashes with 6.2
On 10/26/17 14:26, Cág wrote: > Federico Giannici 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"). > > We had a discussion in the ports@ list a couple of days ago: > https://marc.info/?t=15085986372&r=1&w=2 Had these intermittent Chrome start-up crashes since at least OpenBSD 6.0, but now they seem to be gone with the latest package from -current (brazenly installed on 6.2, as suggested on ports@). Also an issue for Iridium (crashes about every 5 launches). By the way, on i386 Chrome has become unusable for me after updating to 6.2 (extensions crash on start, only simple pages such as openbsd.org load, but the rendering process associated with the tab still crashes after a few seconds). Also, netsurf on i386 crashes every time for me with 6.2, even with no saved settings. The errors look similar: netsurf-gtk(18043) in free(): use after free 0x831b7420 Will look into using sendbug(1) for the first time. If anyone wonders if there's still a usable (possibly full-blown) browser for i386, I'm running SeaMonkey and Iridium (the latter for some web apps, such as Google Music). Firefox has got too bloated, especially since 52.x builds (starting with 6.1) use multiple processes and GTK+ 3.x. In the end, a plea to the awesome maintainer(s) of the most usable Chromium BSD port: please consider Chrome/Iridium binary updates for -stable, as the amazing Landry Breuil builds for Firefox and Thunderbird since 6.1. Not sure many people know about these third-party updates, more at http://undeadly.org/cgi?action=article&sid=20170425173917. Shoutouts to the wonderful people of M:Tier too, I use their binary updates as well! Sadly, -current on amd64 is not an option for me, as I use OpenBSD for work too and need to run a custom Python runtime, only built for -release. And using -current on i386 (for my home router / AP / multimedia station) is too painful… Thanks for the great releases! ;-] signature.asc Description: OpenPGP digital signature
Re: Chrome crashes with 6.2 (Please update official download sites!)
On 10/26/17 13:26, Cág wrote: Federico Giannici 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"). We had a discussion in the ports@ list a couple of days ago: https://marc.info/?t=15085986372&r=1&w=2 I installed the current snapshot package (chromium-61.0.3163.100p1.tgz) and it solved the problem! Now I can use chrome again... As this snapshot package will soon disappear for new ones with incompatible dependences, I think that it would be VERY useful for A LOT of people that this package be put in the official download sites. Thank you
Re: Chrome crashes with 6.2
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 -- on prompt do: bt and hit enter. And please send it here. Thanks! On Thu, Oct 26, 2017 at 12:54 PM, Federico Giannici 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. >
Re: Chrome crashes with 6.2
Federico Giannici 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"). We had a discussion in the ports@ list a couple of days ago: https://marc.info/?t=15085986372&r=1&w=2 -- caóc
Chrome crashes with 6.2
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.
