Some ideas to diagnose it further: - Check via the task manager that you don't have any stray processes hanging around that are pointed at the site, then load the troublesome site in a new tab. (This should cause Chrome to spawn a new process for the page, which could help expose memory issues.) - See whether you can highlight the links or nearby parts on the page by dragging with your mouse, or whether you get the I-beam cursor on the near the links. (This would isolate the issue specifically to links versus general mouse input handling.)
On Wed, Jul 24, 2013 at 4:20 PM, Brad Karp <[email protected]> wrote: > Thanks for trying all the same! > > I'm on amd64. > > Will log a while and see what I come up with. > > On Jul 25, 2013, at 12:18 AM, George Liaskos <[email protected]> > wrote: > > > Unfortunately i can't reproduce this, I am on 9.1-STABLE r253102 amd64. > > > > Are you on amd64 or i386? You can try to enable logging and see if > there's any hint, > > start chrome with --enable-logging=stderr and optionally --v=1 > > > > _______________________________________________ > [email protected] mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-chromium > To unsubscribe, send any mail to "[email protected] > " > _______________________________________________ [email protected] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-chromium To unsubscribe, send any mail to "[email protected]"
