Closed xsmile closed 7 years ago
THANKS
@xsmile can you give a temporary binary
for let people with shitty computers update to chromium 59 (gcc7, apng and gtk3 based) ?
a binary like inox-bin
No, sorry. gcarq should review it first. A working binary doesn't mean the patchset is working as intended.
@xsmile i could test it LOL
@xsmile Does the VA-API patch work without degrading the browser experience? I've heard of some conflicts with the sandboxing mechanism before.
@eloston i offfer me as tester
@Eloston: Can you provide an example? I read a while back that the patch needs further changes and might be problematic for Amd and Nvidia users.
I didn't run any extensive benchmarks. intel_gpu_top shows a GPU usage increase and the CPU usage drops by ~50% when viewing some sample videos on youtube in comparison to the official chromium package. Apart from that I didn't notice anything unusual.
@xsmile I am referring to this comment. Do you need to make a component build and disable the GPU sandbox to get this patch to work?
Also, have you noticed any stability or perfomance issues over longer browsing sessions?
@Eloston: No. However I can only speak for myself as an Intel GPU user.
I will try not to close the browser for a while and post an update if I notice anything unusual.
@xsmile Oh, that's nice. I also use an Intel GPU, so I'll try this out when I get around to it.
@Eloston Everything is fine so far.
I created PR #81 and I'm closing this issue.
I adjusted the patchset for 59.0.3071.86 and the PKGBUILD based on the Arch Linux packages chromium, chromium-dev. Notable changes in contrast to the previous version are:
Issues I noticed so far:
This is by no means a final version and is only meant to help keeping the patchset up-to-date. The new chromium source can still contain unwanted changes not yet accounted for.
[Link removed]