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.
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.
Yuri
_______________________________________________
[email protected] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-chromium
To unsubscribe, send any mail to "[email protected]"
