I have two Rasplex boxes and both are freezing extremely often.
I suspect that the issue is related to processing a new event from the remote, when another operation is in progress, but I can’t confirm it.
Is there any way to make the Rasplex more stable? It’s really annoying.
Does your power supply enough juice?: https://www.raspberrypi.org/help/faqs/#powerReqs
What kind of sd card do you use?
@happycerberus said:
I have two Rasplex boxes and both are freezing extremely often.I suspect that the issue is related to processing a new event from the remote, when another operation is in progress, but I can’t confirm it.
Is there any way to make the Rasplex more stable? It’s really annoying.
I’ve experienced this a bit with 1.0.3. What kind of PI setup do you have?
This is power supply issue, you need at least 2A for RPi0/1/2 and 2.5 A for RPi3, also check the Cable, cheap, thin cables cause a voltage drop, RPi’s are very fussy with power.
Regards
I’ve got the official power supply for my Pi2 (and no peripherals attached) and it still freezes regularly, about once a day but never while I’m watching anything.
@dawtmaytrikx said:
I’ve got the official power supply for my Pi2 (and no peripherals attached) and it still freezes regularly, about once a day but never while I’m watching anything.
I use the Canakit 2.5a with my Pi2 which helped a lot but never completely got rid of the issue. Really I have fewer problems now with less reboots overall. Before I switched, I was getting getting reboots (often when the PI had been sitting unused but powered up for long periods of time) during menu changes and when I started or stopped media. Never in the middle of playback.
Now I get more freezes occuring but not reboots. I’m wondering if this is network and SD card related. Perhaps the PI firmware or Rasplex isn’t responding to certain conditions very well and freezes up. Sometimes these conditions can be really hard to capture.
Is there PI dump data we can retrieve to help diagnosis these problems? I might take look over at their forums.
Are you using CEC? Is the RPi actually ‘frozen’ or just not responding to remote input? I have one old Panasonic TV that appears to have ‘frozen’, however, if I change input source away from Rasplex and then back again it solves the problem. This is because CEC is implemented slightly differently by different manufacturers.
One way to check this is to hook up a USB keyboard, when the RPi appears to freeze, try navigating with the keyboard.
If Rasplex ‘dies’ it should create a crash file on restart, the crash ID can be logged as an issue on GitHub and it will be looked at.
If you believe that Rasplex has frozen, do not pull the power, just SSH in and issue the command - killall plexhometheater
I leave all of my RPi’s on 24/7 and with the exception of the case above have never experienced a ‘frozen’ RPi, (using public pre-release or stable builds) although I understand that it could be frustrating if this happened continuously.
Regards
@NedtheNerd
Is that dump file auto uploaded?
For my system, I’m using WiFi remotes (instead of CEC) and WiFi dongles which have always brought up the power draw issue. I’ll start a clean image with a cat line and try using the iOS Plex app on my phone as a remote.
Yes, just file an issue on GitHub quoting the crash ID and what actions caused the crash.
Regards
rPi3 running OpenPHT/Rasplex 1.6.0
Just took a GUI freeze with no crash when attempting to play a video. Looks like the video component has resource problems and couldn’t break out the loop. I was able to SSH in and restart after nabbing the logs so it wasn’t frozen completely.
04:44:41 T:1767891936 DEBUG: CPlexGlobalTimer::Process firing callback remoteSubscriberManager - spent 0 in queue
04:44:41 T:1767891936 DEBUG: CPlexGlobalTimer::Process waiting 48279 milliseconds for networkServiceBrowser…
04:44:41 T:1314911200 DEBUG: CPlexRemoteSubscriberManager::OnTimeout starting with 1 clients
04:44:41 T:1314911200 DEBUG: CPlexRemoteSubscriber::shouldRemove will not remove because elapsed: 10
04:44:41 T:1314911200 DEBUG: CPlexRemoteSubscriberManager::OnTimeout 1 clients left after timeout
04:44:41 T:1314911200 DEBUG: CPlexGlobalTimer::SetTimeout adding timeout: remoteSubscriberManager at pos 0 [10000]
04:44:41 T:1767891936 DEBUG: CPlexGlobalTimer::Process waiting 9999 milliseconds for remoteSubscriberManager…
04:44:44 T:1809834976 ERROR: COMXCoreComponent::DecoderEventHandler OMX.broadcom.video_decode - OMX_ErrorInsufficientResources, insufficient resources
04:44:51 T:1767891936 ERROR: Previous line repeats 1 times.
See attached for longer log excerpt. Can someone in the know offer whether this information is worth raising a GitHub issue about?
GitHub issue please,
Regards
In addition to logs can you also supply details of the file you are getting this with - media info.
Regards
@NedtheNerd
Thanks, Ned. Done.
