Did you try to upgrade just Chromium or the kernel and not both ?As soon as I update, the problems start to occur.
Not only should we have noticed it, but the forum, github and our inboxes should be flooding with other users reporting the issue as well.Schlendrian wrote: If any of the developers reads this: Please fix the problems. They are reproducable, and you should have noticed them several months ago.
How long is a moment?Schlendrian wrote: After updating Raspbian (2018-06-27) to the latest version, Chromium Browser starts lagging and hanging after a moment while watching YouTube.
I seriously doubt it. The second latest Kernel version was absolutely broken, and the only person complaining about all the problems was someone on a German forum.
Maybe 5 to 10 minutes. Sometimes it takes only a few seconds. It varies.How long is a moment?
I'm sorry, but I don't believe that.Just played a few 1080p videos off youtube without any problems.
Always 64 MB, since allocating more RAM doesn't change anything. "free -h" shows enough free memory, but starts swapping 6 MB for some reason. I deleted the swap file and disabled swapping, but it also didn't change anything.How much GPU RAM do you have allocated? What does 'free -h' say before and after it starts lagging?
Schlendrian wrote:I seriously doubt it.
If we start with the premise that I'm a compulsive liar, I can't help you.Schlendrian wrote:I'm sorry, but I don't believe that.
I didn't call you a liar nor a "compulsive" liar. Please, stop ripping things out of context and playing the "you hurt my feelings"-card.
Yes, it definitely is. I'm running 65.0.3325.181 right now, and it's absolutely broken.
I'm running the same v65, and I can run 720p videos on YouTube fine.Schlendrian wrote: ↑Fri Oct 05, 2018 1:01 pmYes, it definitely is. I'm running 65.0.3325.181 right now, and it's absolutely broken.
That is the same kernel version I am running. 4.14.70-v7+. ??Schlendrian wrote: ↑Fri Oct 05, 2018 1:11 pmWell, I just noticed, that it's the same version that comes with Raspbian 2018-06-27. Strangely it downloaded an updated version, but the version number didn't change at all (why?).
So, either it's this new version (that somehow has no new version number), that causes the problems (which is hard to tell, since version numbers didn't change), or it's Kernel related, because I'm now running on 4.14.70-v7+.
My guess is, it's the Kernel. The last version was so broken, you couldn't even shutdown Raspbian anymore and the Pi would freeze randomly.
When this happens, what does 'vcgencmd get_throttled' report? What pi model is this? Mostly interested in the omxplayer case, because there's the least that could go wrong there. Does it happen with any video at all regardless of resolution and codec?mikekscholz wrote: ↑Fri Oct 05, 2018 1:35 pmIve been having these problems as well.... Like to a T. And ive been running my memory split at 256 from the beginning because this is mainly intended to be a video pi. I get the cut outs and the phantom loading spin and everything... Nothing fixes it but a reboot for me though. Also when ever it happens it kills my bluetooth and I cant even reconnect my headphones without a reboot either.... Same problems have been happening with all videos... omx player, and FFmpeg with mpv... Im currently in process of clean install and rebuild of FFmpeg..... Again.
It's impossible to run videos in [email protected] at a desktop resolution of 1080p on a Pi.
If you know the RPi can't do it, then why are you trying to stream it?Schlendrian wrote: ↑Fri Oct 05, 2018 1:55 pmIt's impossible to run videos in [email protected] at a desktop resolution of 1080p on a Pi.
I have been running this at 30fps by disabling 60fps via the h264ify extension.
What does this "I have been running this at 30fps by disabling 60fps via the h264ify extension." tell you?
How often do I have to repeat myself? I wrote several times: At a desktop resolution of 1080p.BTW, my version resorts to 480p to stream it. My Tinker Board resorts to 720p/60fps to stream it. Maybe you need more butt to do what you want.
I wasn't going to reply based on the bad karma behavior here, but our local group did encounter a vc4 glitch that would hang X11 once in awhile if using the 3D accelerated module.
I'm not a Hindu, so I don't care about their concept of being reborn.
You can also play locally stored 1080p videos via Chromium. It works out of the box. No need for VLC or Kodi.
but our local group did encounter a vc4 glitch that would hang X11 once in awhile if using the 3D accelerated module.
Several months ago, I simply went to the kernel vc maintainers git bug report page with the logs, and ended up getting a patch from their kind maintainers to build the custom pi3B+ kernel we needed: https://sourceforge.net/projects/microm ... spberry-pi
Since the RTlinux Stretch OS is based on an read-only overlayfs root, it is actually initially version locked to a clone of my desktop. However, note the documented "reload the browser once" bug... you need to restart the browser on a plug-in page once to properly get the vc4 memory work-around to load.
I used midori and not chromium given the project focus is on the machinery we used, and VLC with gpu support will play 720p full screen h264 if the file is opened locally. We use this classic video to benchmark various setups:
I have a 125 MBit Internet connection. I don't think, it's my network. YouTube only need a maximum of 150 KB to play a video at 720p.
It could also be your network is under heavy use and is throttling your streams, or you have various background updates running (my pet peeve about systemd). My pi3B+ has been noticeably faster than the older pi3, does draw more power, and requires fan blown heat-sinks to run full 100% loads over a few seconds (or it will throttle back due to temperature).
sudo cat /etc/systemd/journald.conf
This doesn't do anything cups.service couldn't even be found (maybe, because I dont't have printer set up?).
I have a heat sink. Overheating is not the problem. The problem is, that things don't work with the newest updates, that worked flawlessly beforehand.#or during a test playback run this in a terminal to see if you pinned the cpu cores...
#you may find the CPU heat sink may be needed
Well, I surely appreciate any help. I didn't insult anyone, and I'm also not angry. I'm only very disappointed, because I use the Pi as my main system (I don't see, why I should pay 400€ and more for a "normal" PC, if a 35€ PC does exactly the same), and I need a reliable system to work with. It can't work with a randomly freezing system.You should still consider apologizing to the people that took the time to try and assist you. Getting angry won't help you, as I have known a few ex-service people over the years with high-stress cortisol related burn-out, and it is just an unhealthy way to live as several international institutional studies have proven.