Raspberry Pi running installer at almost 400%

Answered

Comments

12 comments

  • Avatar
    İTÜ System Support Team
    I have many RPi 3 RisePlayer installation inside my networks. I expreience same issue in almost all of my RPis.

    Issue is, after reboot, installer script applies the new RisePlayer update. Then restarts player with new one within /tmp directory.
    pi         671 10.0 10.9 503756 97776 ?        Sl   15:21   0:58 /home/pi/rvplayer/2017.09.11.22.45/Installer/installer --unattended --skip-countdown
    pi         686  0.0  2.3 127032 20856 ?        S    15:21   0:00  \_ /home/pi/rvplayer/2017.09.11.22.45/Installer/installer --type=zygote --no-sandbox
    pi         821  1.0  5.4 240916 49220 ?        Ssl  15:21   0:06  \_ /home/pi/rvplayer/2017.09.11.22.45/Installer/installer /home/pi/rvplayer/2017.09.11.22.45/Installer/resource  
    s/app.asar/node_modules/rise-cache-v2/rise-cache.js
    pi         831  0.1  0.0      0     0 ?        Zs   15:21   0:00  \_ [installer] <defunct>
    pi         884  0.0  0.1   1900  1216 ?        Ss   15:22   0:00  \_ /bin/sh /tmp/rvplayer-2017.09.11.22.45-1508934087211/installer-lnx-armv7l.sh --nox11 -- --unattended --skip-  
    countdown
    pi        1041  0.0  0.2   5000  2528 ?        S    15:22   0:00      \_ /bin/bash ./2017.10.16.19.40/initial-run.sh --unattended --skip-countdown
    pi        1081  7.8 10.5 632204 94604 ?        Sl   15:22   0:40          \_ /home/pi/rvplayer/2017.10.16.19.40/Installer/installer --unattended --unattended --skip-countdown
    pi        1083  0.0  2.6 131756 24104 ?        S    15:22   0:00              \_ /home/pi/rvplayer/2017.10.16.19.40/Installer/installer --type=zygote --no-sandbox
    pi        1128  0.1  5.8 262324 52480 ?        Sl   15:22   0:00              |   \_ /home/pi/rvplayer/2017.10.16.19.40/Installer/installer --type=renderer --no-sandbox --primor  
    dial-pipe-token=59241BE55A8011AF4C008BCBD9675305 --lang=en-GB --standard-schemes=rchttp,rchttps --secure-schemes=rchttp,rchttps --app-path=/home/pi/rvplayer/2017.10.16.19.40/Ins  
    taller/resources/app.asar --node-integration=true --webview-tag=true --no-sandbox --enable-pinch --num-raster-threads=2 --enable-main-frame-before-activation --content-image-tex  
    ture-target=0,0,3553;0,1,3553;0,2,3553;0,3,3553;0,4,3553;0,5,3553;0,6,3553;0,7,3553;0,8,3553;0,9,3553;0,10,3553;0,11,3553;0,12,3553;0,13,3553;0,14,3553;0,15,3553;1,0,3553;1,1,35  
    53;1,2,3553;1,3,3553;1,4,3553;1,5,3553;1,6,3553;1,7,3553;1,
    pi        1167 18.0 31.6 561004 283624 ?       Sl   15:22   1:28              |   \_ /home/pi/rvplayer/2017.10.16.19.40/Installer/installer --type=renderer --no-sandbox --primor  
    dial-pipe-token=CB397A8A8DD178A424A41AF39FFE426B --lang=en-GB --standard-schemes=rchttp,rchttps --secure-schemes=rchttp,rchttps --app-path=/home/pi/rvplayer/2017.10.16.19.40/Ins  
    taller/resources/app.asar --enable-plugins --node-integration=false --webview-tag=false --no-sandbox --preload=/home/pi/rvplayer/2017.10.16.19.40/Installer/resources/app.asar/vi  
    ewer/preload.js --enable-pinch --num-raster-threads=2 --enable-main-frame-before-activation --content-image-texture-target=0,0,3553;0,1,3553;0,2,3553;0,3,3553;0,4,3553;0,5,3553;  
    0,6,3553;0,7,3553;0,8,3553;0,9,3553;0,10,3553;0,11,3553;0,1
    pi        1113  353 17.5 367968 157404 ?       Sl   15:22  29:40              \_ /home/pi/rvplayer/2017.10.16.19.40/Installer/installer --type=gpu-process --no-sandbox --support  
    s-dual-gpus=false --gpu-driver-bug-workarounds=7,23,74 --disable-gl-extensions=GL_KHR_blend_equation_advanced GL_KHR_blend_equation_advanced_coherent --gpu-vendor-id=0x0000 --gp  
    u-device-id=0x0000 --gpu-driver-vendor --gpu-driver-version --gpu-driver-date --service-request-channel-token=9D06750929C16EDF0047DC00C02A02BC
    pi        1158  1.1  6.7 242132 60884 ?        Ssl  15:22   0:05              \_ /home/pi/rvplayer/2017.10.16.19.40/Installer/installer /home/pi/rvplayer/2017.10.16.19.40/Instal  
    ler/resources/app.asar/node_modules/rise-cache-v2/rise-cache.js
    pi        1162  0.1  4.3 153396 38784 ?        Ssl  15:22   0:00              \_ /home/pi/rvplayer/2017.10.16.19.40/Installer/installer /home/pi/rvplayer/2017.10.16.19.40/Instal  
    ler/resources/app.asar/watchdog/index.js
    After next reboot, player start with newly installed up-to-date version. However, gpu-process seems to have different paramaters than old one and this process has the most of CPU consumption %400~.

    root@riseplayer:~# ps -p 701 fww -o user,uid,pid,pcpu,cmd
    USER       UID   PID %CPU CMD
    pi        1000   701  360 /home/pi/rvplayer/2017.10.16.19.40/Installer/installer --type=gpu-process --no-sandbox --supports-dual-gpus=false --gpu-driver-bug-workarounds=7,23,74 --disable-gl-extensions=GL_KHR_blend_equation_advanced GL_KHR_blend_equation_advanced_coherent --gpu-vendor-id=0x0000 --gpu-device-id=0x0000 --gpu-driver-vendor --gpu-driver-version --gpu-driver-date --service-request-channel-token=4E77B5580FC456D8DF78F4922797009C
    root@riseplayer:~#
    new parameters : - --type=gpu-process --no-sandbox --supports-dual-gpus=false --gpu-driver-bug-workarounds=7,23,74 --disable-gl-extensions=GL_KHR_blend_equation_advanced GL_KHR_blend_equation_advanced_coherent --gpu-vendor-id=0x0000 --gpu-device-id=0x0000 --gpu-driver-vendor --gpu-driver-version --gpu-driver-date --service-request-channel-token=4E77B5580FC456D8DF78F4922797009C

    old parameters :  --type=gpu-process --no-sandbox --supports-dual-gpus=false --gpu-driver-bug-workarounds=7,23,71 --gpu-vendor-id=0x0000 --gpu-device-id=0x0000 --gpu-driver-vendor --gpu-driver-version --gpu-driver-date --service-request-channel-token=A3EF94F5DFEA95E6650DA8DDCA60D051 --v8-natives-passed-by-fd --v8-snapshot-passed-by-fd

    I have a clean image to restore old version installation on my RPis however, i need a parameter to discard updates for my RisePlayers... Please share the paramaters:
    https://community.risevision.com/rise_vision_inc/topics/rise-player-raspberry-pi-parameters-for-inst...

    This is an urgent issue...
  • Avatar
    İTÜ System Support Team
    New Version : RisePlayerElectron 2017.10.16.19.40
    Old Version : RisePlayerElectron 2017.09.11.22.45
  • Avatar
    Alan Clayton
    Thanks for the feedback. Could you please email us the Display ID's to support@risevision.com
  • Avatar
    İTÜ System Support Team
    Is there any update on the issue?
  • Avatar
    Niclas Hallgren
    Thanks for the answer, I've emailed my Display ID to support. I'm also running RisePlayerElectron 2017.10.16.19.40 Standard
  • Avatar
    Alan Clayton
    What you are seeing appears to be a result of upgrading Chromium version. RisePlayerElectron 2017.10.02.15.28 shipped with Chromium version 56 and RisePlayerElectron 2017.10.16.19.40 shipped with Chromium version 58.

    While we work through this you can download and install RisePlayer 2017.10.02.15.28 from here

    We'll provide additional updates as we work this through. 

    Thanks
  • Avatar
    Niclas Hallgren
    Hi again, I noticed that when I replaced my running presentation with a very simple one everything goes back to normal. The one I normally uses shows two (change every 10 seconds) node.js generated pages with socket.io connection for displaying live information such as a clock and live data from temperature sensors etc. I use the web presentation widget for that. Pages are local only (192.x.x.x) if that is part of the problem...
  • Avatar
    Andrew Cutler
    Thanks for the fix. I've just reinstalled with the version linked above and all appears to be back to normal.
  • Avatar
    İTÜ System Support Team
    Alan, thanks for update.

    I do not understand one thing. While i use "RisePlayerElectron 2017.09.11.22.45", my clients upgrade the installer version after reboot. That is why i ask for a solution to prevent auto-updates.

    Now the installer version you provide (2017.10.02.15.28), did not apply an upgrade. I need to understand the installer/player 's behaviour, before i deploy more Rise Player inside campus network.

    Also is there an up-to-date public repository in order to contribute, examine the project and follow issues?
  • Avatar
    Alan Clayton
    You can find the public repository for Rise Player here, https://github.com/Rise-Vision/rise-launcher-electron

    The reason your clients were upgrading after a reboot was because we had the rollout for the 2017.10.16 release applied to all Displays. In other words, any instance of Rise Player that was not 2017.10.16 would auto upgrade to that version. 

    The reason your Display is no longer auto upgrading is because we stopped the rollout for the 2017.10.16 release which means Player will run whatever version it has installed.

    We do not currently support the ability for a Display to opt out of upgrades, but recognize the current process can be improved upon. I describe in this conversation the direction we have discussed as an improvement. Take a read and let me know your feedback. 

    Thanks!
  • Avatar
    Andrew Cutler

    Hi Alan,

    Can you please change the version being downloaded from https://help.risevision.com/hc/en-us/articles/115001872303-Install-Rise-Player-on-Pi to the fixed version? It seems pointless to keep downloading a faulty version.

     

    Thanks,

    Andrew

  • Avatar
    Alan Clayton

    Hi Andrew, the Rise Player Installer for Pi provided in the Help Documentation and Displays App have been updated. 

    Thanks!

Please sign in to leave a comment.