Did you switch to the Chrome OS beta channel recently? It's time to move back to Stable!

  • 1
  • Announcement
  • Updated 3 years ago
Some of our users were recently affected by an issue Introduced in Chrome 43.0.2357.125. This issue caused Rise Player to crash and restart. At the time of the issue, the only resolution was to advise users to switch to the Chrome OS beta channel.

On Tuesday night, Google released Chrome OS version 43.0.2357.130 which addresses the crashing issue. We monitored the stable channel throughout the day yesterday and have not seen any issues with this update. At this time, we recommend that if you have switched your Chromebox running Rise Player to the Beta channel due to this issue, it's now time to switch back to the Stable channel.
Photo of Blake Freeman

Blake Freeman, Official Rep

  • 36,116 Points 20k badge 2x thumb
  • Thankful

Posted 3 years ago

  • 1
Photo of Thierry Masson

Thierry Masson, Champion

  • 2,356 Points 2k badge 2x thumb
Sorry but what about the topic 'Outage notice: Chrome OS Players' with this reply regarding a problem with the update process to 43.*.130 :

I have published an issue with Google here. It would be a great help if you and anyone else that has experienced this issue would chime in on the issue and state what you have seen. Thanks!

This Chromium issue is still in 'Open Issue' status. Can we forget about it ?
Photo of Blake Freeman

Blake Freeman, Official Rep

  • 36,116 Points 20k badge 2x thumb
Thierry,

The issue that I logged with Google yesterday is regarding an unexpected shut down due to devices auto-updating to .130. This has been witnessed by two users on the forum, but I have been unable to replicate the issue. The update to .130 addresses the issue of Rise Player crashing and restarting. It functions for it's intended purpose.

The unexpected shutdown after a new Chrome version is released is an issue that we are trying to get input on to replicate. It should not dissuade anyone from updating to .130 in the meantime.
Photo of Thierry Masson

Thierry Masson, Champion

  • 2,356 Points 2k badge 2x thumb
Thanks Blake.
As mentioned in another thread, this night, one of my non-managed Chromebox made an auto-update to 43.*130 successfully and did not shutdown.
The rest of the CB are managed with no auto-update. They are in 43.*.125.
I'm hesitating to enable auto-update to *.130.
Photo of Blake Freeman

Blake Freeman, Official Rep

  • 36,116 Points 20k badge 2x thumb
Thierry,

The shutdowns due to Chrome OS updates are at this point not wide-spread. We have had two users mention that they have had this issue, but have not witnessed it in house.
Photo of Blake Freeman

Blake Freeman, Official Rep

  • 36,116 Points 20k badge 2x thumb
This reply was created from a merged topic originally titled Outage notice: Chrome OS Players..

Hello all,

At 12:20 PM CST we were informed by multiple users that their Chromeboxes running the Rise Vision Player were crashing.

We have identified the issue, and a fix is pending release from the Chrome App Store.

We are sorry for any inconvenience this may have caused you. This topic will be updated as news is available.
Photo of Engineered Glass IT

Engineered Glass IT

  • 686 Points 500 badge 2x thumb
The new .130 on the stable channel seems to fix the crashing issues I had. No shutdowns on three of my chromeboxes in the past 24 hours

I am one of the two users who reported the issue ;) 
(Edited)