Date: Mon, 28 Oct 2013 14:22:19 -0700 From: Evan Martin <evan@chromium.org> To: Yuri <yuri@rawbw.com> Cc: chromium@freebsd.org Subject: Re: Why Google street view scrolls not very smoothly in Chrome? Message-ID: <CAFzwtj23d2njWSXMF97b%2B-4dafJdNLBiC7uVgNQ%2B%2B8h6VOZZ6w@mail.gmail.com> In-Reply-To: <526C3BEF.1020409@rawbw.com> References: <5265ED2F.7030009@rawbw.com> <CAFzwtj1_C8tzm2MZr1kJjfig1wU_WmpTPtMELDWUuN-4R0L6LQ@mail.gmail.com> <526C3BEF.1020409@rawbw.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, Oct 26, 2013 at 3:02 PM, Yuri <yuri@rawbw.com> wrote: > On 10/22/2013 09:21, Evan Martin wrote: > >> 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. :) >> > > "use hardware acceleration when available" is set, but the problem occurs > nevertheless. > You misread. I suggested *un*checking "use hardware acceleration". (Chrome's hardware acceleration support works better on platforms with better GL drivers; in my experience it makes things worse on Linux, at least.) However, this isn't relevant because of the below: I did some investigation. The same flash street-view object is instantiated > in exactly the same way in both chrome and firefox. (DOM branch > corresponding to flash is identical in both browsers). But there is still > the difference in behavior as I explained in my OP. > > On 4-core machine in firefox, flash itself pops up in top(1). 4 > npviewer.bin processes go up to ~40% CPU each, and Xorg is also at 40%. > > In chrome Xorg goes to 100% CPU, and this "stickiness" occurs. > > From the above I conclude that some plugin callbacks into the browser > either behave differently, or are invoked differently in chrome. > > Is there any way to log the communication with instantiated plugin in > chrome? > > One other difference in behavior is that in chrome right mouse click > doesn't cause the standard flash menu (with Global Settings amd About > items) to appear. Ah, you're using nspluginwrapper. Unfortunately, nspluginwrapper just doesn't work very well with Chrome. nspluginwrapper is actually unmaintained, and in working on Chrome for Linux we ran into so many problems with it that one of the Chrome developers took over maintainership in an attempt to fix some bugs! But in practice I don't think it'll ever work well. http://nspluginwrapper.org/ => last release was June 2011.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAFzwtj23d2njWSXMF97b%2B-4dafJdNLBiC7uVgNQ%2B%2B8h6VOZZ6w>