Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 19 Feb 2016 06:39:48 +0000
From:      bugzilla-noreply@freebsd.org
To:        chromium@FreeBSD.org
Subject:   [Bug 204454] www/chromium Aw Snap! with pages containing javscript
Message-ID:  <bug-204454-28929-XbmElhbmYV@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-204454-28929@https.bugs.freebsd.org/bugzilla/>
References:  <bug-204454-28929@https.bugs.freebsd.org/bugzilla/>

next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D204454

--- Comment #10 from Wayne Sierke <ws@au.dyndns.ws> ---
(In reply to Arto Pekkanen from comment #9)
Yes, unfortunately while my initial experience was much improved over earli=
er,
recent versions, longer-term use has shown that the issue is very much still
present. I do feel that it is somewhat improved, particularly on initial st=
art,
but over time it slowly deteriorates. I haven't encountered any pages that
won't normally reload correctly straight away - with the exception of
kickstarter, which currently crashes the browser altogether - but that I
believe is a separate issue linked to something else that got upgraded.

On the whole if "feels" like it's correlated to resource-usage (primarily
memory). The page failures seem to occur more often the longer chromium is
running and as its resource usage rises.

--=20
You are receiving this mail because:
You are the assignee for the bug.=



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-204454-28929-XbmElhbmYV>