https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212812
Scott Hazen Mueller <sc...@zorch.sf-bay.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |sc...@zorch.sf-bay.org
--- Comment #79 from Scott Hazen Mueller <sc...@zorch.sf-bay.org> ---
(In reply to Rob Belics from comment #34)
There must be multiple failure modes. I found this technique to work for hung
tabs @ www.wunderground.com (which usually takes 3-5 attempts to render a
single page, using this I could navigate the site freely) but facebook locked
up a few clicks in as usual.
I've tried tmpfs, linking cache to /dev/null, disabling gpu, disabling v8,
nothing has gotten me a stable chromium. WU is my normal test case, now I'm in
a mode where it works and FB is reasonably unreliable.
I'm running 11.1 release on an Intel Core Duo 6400 processor, 4GB of RAM (some
unused because architecture), dual 250GB mirrored SSDs, an Nvidia-based
graphics card (GeForce GT 610), nothing special, fairly old hardware.
--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
freebsd-chromium@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-chromium
To unsubscribe, send any mail to "freebsd-chromium-unsubscr...@freebsd.org"
