Re: Crashing chromium/iridium

[G. Paul Ziemba]

j...@chen.org.nz (Jonathan Chen) writes:

>On 7 October 2017 at 08:39, Grzegorz Junka  wrote:
>> Just wanted to check if anybody else observed this annoying behaviour in
>> Chromium/Iridium browsers. Randomly, in about 10-40% of cases, the new tab
>> hangs loading for 30-60 seconds, after which time the browser shows a dialog
>> that the webpage doesn't load and I can either kill or wait.

>This bug has been around for a very long time:
>https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212812

>There was some anecdotal evidence that it was related to code-caching,
>with a possible workaround, but no fixes for it have been committed.
>The workarounds do not appear to work anymore with the latest updates,
>though.

The following applies to FreeBSD 11-stable.

I did not experience the issue with 51.0.2704.84, but have seen it
since chrome 59.0.3071.115. I also tried 60.0.3112.101 and 61.0.3163.100
(more recent versions of the www/chromium port) with no improvement.

Might be an independent bug, but I am also getting a "file not found"
error when I click on "options" for the three different plugins I was
using ("ublock origin", "tabs outliner", and "go back with backspace").
This broken behavior could be fixed temporarily by deleting and then
reinstalling the plugin, but after a day or so it would return.

I found that I could recover from the "some tabs hanging forever" state by:

1. Quit chrome browser
2. Delete cache in ~/.cache/chromium or wherever (I am using
   --user-data-dir=/my/homedir/.config/chrome-myhostname, and
   it appears to affect the path in ~/.cache as well)
3. Delete user data dir (in my case, /my/homedir/.config/chrome-myhostname)
4. Restore Bookmarks file (I copy it via cron every day)
5. Reinstall "ublock origin". I abandoned the other two plugins
   because T.O. couldn't access its configuration and the backspace
   plugin stopped working (grr)

That is a drastic approach because all configuration and state is
lost, but it did seem to overcome the hanging tab problem. It makes
me think that there is some persistent state in chrome's user directory
that is related to this issue.

I tried building www/chromium 61 with DEBUG, but the build failed, and I
have not pursued it further.
-- 
G. Paul Ziemba
FreeBSD unix:
 1:41PM  up 9 days, 23:29, 14 users, load averages: 0.38, 0.35, 0.29
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Crashing chromium/iridium

[Jonathan Chen]

On 7 October 2017 at 08:39, Grzegorz Junka  wrote:
> Just wanted to check if anybody else observed this annoying behaviour in
> Chromium/Iridium browsers. Randomly, in about 10-40% of cases, the new tab
> hangs loading for 30-60 seconds, after which time the browser shows a dialog
> that the webpage doesn't load and I can either kill or wait.

This bug has been around for a very long time:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212812

There was some anecdotal evidence that it was related to code-caching,
with a possible workaround, but no fixes for it have been committed.
The workarounds do not appear to work anymore with the latest updates,
though.

CHeers.
-- 
Jonathan Chen 
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Crashing chromium/iridium

[Kyle Evans]

For reference: there's been some escalation of this by asmodai@ (I think --
don't quote me on this): https://bugs.chromium.org/p/chromium/issues/detail?
id=729534 -- asmodai@ was requesting some help in further debugging, but
unfortunately does not seem to have received any help in that regard.


On Fri, Oct 6, 2017 at 2:40 PM, Domagoj Stolfa 
wrote:

> I’ve found this to be an issue as well. None of the things that I’ve seen
> suggested online could fix it, and unfortunately do not have time to look
> at it myself. I’d be interested to hear if anyone has any more details
> regarding this issue.
>
> —
> Domagoj
>
> > On 6 Oct 2017, at 20:39, Grzegorz Junka  wrote:
> >
> > Just wanted to check if anybody else observed this annoying behaviour in
> Chromium/Iridium browsers. Randomly, in about 10-40% of cases, the new tab
> hangs loading for 30-60 seconds, after which time the browser shows a
> dialog that the webpage doesn't load and I can either kill or wait.
> >
> > There is no pattern, sometimes I can open 10 tabs with no issues, but
> sometimes 10 tabs hang in a row and need to be killed. Very often when I
> kill the page reloading the page doesn't help, it still hangs, but when I
> open the same URL in a new tab it works. Sometimes, however, reloading the
> page also works.
> >
> > I compiled and installed Iridium hoping that it will be free from this
> bug but it seems that the behaviour is exactly the same as in Chromium. It
> has been happening for the past year at least. Maybe some of the options I
> checked for Chromium/Iridium don't work well or maybe some of its
> dependencies are compiled with options that don't work well. How would I
> investigate it?
> >
> > I didn't try to install precompiled versions. Also, the issue doesn't
> happen with other browsers (Firefox, any other I could compile on FreeBSD
> are also fine). I tried to open in safe mode, without extensions, but all
> without any difference in this behaviour.
> >
> > Thanks
> >
> > GrzegorzJ
>
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Crashing chromium/iridium

[Domagoj Stolfa]

I’ve found this to be an issue as well. None of the things that I’ve seen 
suggested online could fix it, and unfortunately do not have time to look at it 
myself. I’d be interested to hear if anyone has any more details regarding this 
issue.

—
Domagoj

> On 6 Oct 2017, at 20:39, Grzegorz Junka  wrote:
> 
> Just wanted to check if anybody else observed this annoying behaviour in 
> Chromium/Iridium browsers. Randomly, in about 10-40% of cases, the new tab 
> hangs loading for 30-60 seconds, after which time the browser shows a dialog 
> that the webpage doesn't load and I can either kill or wait.
> 
> There is no pattern, sometimes I can open 10 tabs with no issues, but 
> sometimes 10 tabs hang in a row and need to be killed. Very often when I kill 
> the page reloading the page doesn't help, it still hangs, but when I open the 
> same URL in a new tab it works. Sometimes, however, reloading the page also 
> works.
> 
> I compiled and installed Iridium hoping that it will be free from this bug 
> but it seems that the behaviour is exactly the same as in Chromium. It has 
> been happening for the past year at least. Maybe some of the options I 
> checked for Chromium/Iridium don't work well or maybe some of its 
> dependencies are compiled with options that don't work well. How would I 
> investigate it?
> 
> I didn't try to install precompiled versions. Also, the issue doesn't happen 
> with other browsers (Firefox, any other I could compile on FreeBSD are also 
> fine). I tried to open in safe mode, without extensions, but all without any 
> difference in this behaviour.
> 
> Thanks
> 
> GrzegorzJ
> 
> 
> ___
> freebsd-ports@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-ports
> To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"



signature.asc
Description: Message signed with OpenPGP

Crashing chromium/iridium

[Grzegorz Junka]

Just wanted to check if anybody else observed this annoying behaviour in 
Chromium/Iridium browsers. Randomly, in about 10-40% of cases, the new 
tab hangs loading for 30-60 seconds, after which time the browser shows 
a dialog that the webpage doesn't load and I can either kill or wait.


There is no pattern, sometimes I can open 10 tabs with no issues, but 
sometimes 10 tabs hang in a row and need to be killed. Very often when I 
kill the page reloading the page doesn't help, it still hangs, but when 
I open the same URL in a new tab it works. Sometimes, however, reloading 
the page also works.


I compiled and installed Iridium hoping that it will be free from this 
bug but it seems that the behaviour is exactly the same as in Chromium. 
It has been happening for the past year at least. Maybe some of the 
options I checked for Chromium/Iridium don't work well or maybe some of 
its dependencies are compiled with options that don't work well. How 
would I investigate it?


I didn't try to install precompiled versions. Also, the issue doesn't 
happen with other browsers (Firefox, any other I could compile on 
FreeBSD are also fine). I tried to open in safe mode, without 
extensions, but all without any difference in this behaviour.


Thanks

GrzegorzJ


___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"