Skip to content

Commit bd63daa

Browse files
committedJun 25, 2017
chromium: Add installation of libGLESv2.so
The following errors occur when you start Chromium prior to this commit: [2534:2534:0625/202928.673160:ERROR:gl_implementation.cc(246)] Failed to load .../libexec/chromium/swiftshader/libGLESv2.so: ../libexec/chromium/swiftshader/libGLESv2.so: cannot open shared object file: No such file or directory [2534:2534:0625/202928.674434:ERROR:gpu_child_thread.cc(174)] Exiting GPU process due to errors during initialization While in theory we do not strictly need libGLESv2.so, in practice this means that the GPU process isn't starting up at all which in turn leads to crawling rendering performance on some sites. So let's install all shared libraries in swiftshader. I've tested this with the chromium.stable NixOS VM test and also locally on my machine and the errors as well as the performance issues are gone. Signed-off-by: aszlig <aszlig@redmoonstudios.org>
1 parent c43a2d3 commit bd63daa

File tree

1 file changed

+2
-1
lines changed
  • pkgs/applications/networking/browsers/chromium

1 file changed

+2
-1
lines changed
 

‎pkgs/applications/networking/browsers/chromium/browser.nix

+2-1
Original file line numberDiff line numberDiff line change
@@ -12,10 +12,11 @@ mkChromiumDerivation (base: rec {
1212
sandboxExecutableName = "__chromium-suid-sandbox";
1313

1414
installPhase = ''
15-
mkdir -p "$libExecPath"
15+
mkdir -p "$libExecPath/swiftshader"
1616
cp -v "$buildPath/"*.pak "$buildPath/"*.bin "$libExecPath/"
1717
cp -v "$buildPath/icudtl.dat" "$libExecPath/"
1818
cp -vLR "$buildPath/locales" "$buildPath/resources" "$libExecPath/"
19+
cp -v "$buildPath/swiftshader/"*.so "$libExecPath/swiftshader/"
1920
cp -v "$buildPath/chrome" "$libExecPath/$packageName"
2021
2122
if [ -e "$buildPath/libwidevinecdmadapter.so" ]; then

0 commit comments

Comments
 (0)