One thing to try is to go to Chrome's settings, search for "hardware", and uncheck "use hardware acceleration when available". That uses a different code path (X CopyRects instead of OpenGL calls) that might be faster. As for *why* it's different, blame any of bugs in the port, bugs in the drivers, X's design, or anything else of your choosing. :)
On Mon, Oct 21, 2013 at 8:12 PM, Yuri <[email protected]> wrote: > I open any place in Google maps, then select street view, then move the > image with mouse. > > Chrome does this worse than firefox. Image moves in a jerky way, stopping > many times on the way. Like it periodically sticks. > In firefox the motion is much smoother, but still not perfect. > The problem is especially visible when compared to Windows. (Radeon 7470) > Same street view image on Windows on much less powerful machine moves in > what seems like a completely smooth fashion in FF. > > I would have been inclined to blame NVidia driver (version 319.32, GT > 610). But then why there is such a difference between chrome and FF? > I didn't get a chance to see the same on Windows in Chrome, but I believe > it should look much better than in FreeBSD. > > Is it known why Chrome exhibits worse behavior compared to FF? And why > street view sucks in FreeBSD in general? > > Yuri > ______________________________**_________________ > [email protected] mailing list > http://lists.freebsd.org/**mailman/listinfo/freebsd-**chromium<http://lists.freebsd.org/mailman/listinfo/freebsd-chromium> > To unsubscribe, send any mail to "freebsd-chromium-unsubscribe@** > freebsd.org <[email protected]>" > _______________________________________________ [email protected] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-chromium To unsubscribe, send any mail to "[email protected]"
