That's not the error. The segmentation fault, which you two aren't having is the actual error message and the first has nothing to do with the second.matteusbeus wrote:https://bugs.launchpad.net/ubuntu/+sour ... ug/1563184
Feel free to flag that the issue effects you
Interesting. Can you try and see if v48 has this behavior as well?Dis93 wrote:I've managed to reproduce the behaviour. It's not Chromium crashing, it's the Pi running out of memory and filling the swap too. I had a few tabs open, one never finished loading and the available RAM and then the swap maxed out. The green led stayed lit but I had to yank the power anyway.
Ok. V50 is coming out soon anyway so I won't downgrade everything right now, but if that has the problem as well I'll downgrade.Dis93 wrote:Downgraded to 48.
Managed to open twice as many tabs. Swap maxed out but RAM did not. Swap maxed out more gradually.
System was slow but still responsive.
Ah, then I'll still hold to v49. It's a fast browser, but it uses a lot of RAM.Dis93 wrote:Just crapped out just the same. Took a lot longer though.
AFAIK Chromium/Chrome both suffer from increasing RAM hunger.
I'm not afriend of this "modern" mobile-like program design and so never really liked chrome (but other software looks similar now), but this is nonsense. Since chromium / chrome forked from the webkit engine a lot has happened to make it more effective: multi-threaded, faster Javascript etc.matteusbeus wrote:Increase bloat :/ Chrome used to be pretty good!
Perhaps that is true, but when Chrome/Chromium was first released it put other browsers to shame with its speed. Now it survives by familiarity and a nicer UI than the others. So either Chrome/Chromium has become bloated or the others have become sleeker.gkreidl wrote:I'm not afriend of this "modern" mobile-like program design and so never really liked chrome (but other software looks similar now), but this is nonsense. Since chromium / chrome forked from the webkit engine a lot has happened to make it more effective: multi-threaded, faster Javascript etc.matteusbeus wrote:Increase bloat :/ Chrome used to be pretty good!
The bloat comes from the internet; tons of superfluous Javascript that slows everything down (and more bad design stuff like pages that need 200 elements to load etc.).
That's how much you think modern webpages are? They are way more, look online for true facts. How much do other webbrowsers consume?matteusbeus wrote:You can't blame a few mb of html, images, css and js files on the need for a couple of hundred mb of ram per tab!
My favorite browser as well. Well just have to wait and see. I'm going start compiling the v50 this weekend. It should be done by next week.matteusbeus wrote:It's memory management rather than the use that bothers me. I have simular freeze ups with chrome in windows. It's still my fave browser tho! Fingers crossed they sort out the issues so we can have it running well on the pi!
Yes, it is my browser of choice. I was referring more to Chrome/Chromium on Windows.kusti8 wrote:
It still wins with speed, especially on the Pi. The huge user base of extensions helps as well. Have you even tried Chromium on the Pi?
With the current GPU driver, no, but with the new OpenGL driver, yes there is hardware acceleration.Sandros94 wrote:Hi, can you tell me if I'm wrong about chromium (v49 and next coming v50) doesn't have hardware acceleration?
I was reading around that at the moment OpenGL driver are in beta and are too glitchy for a normal use right?kusti8 wrote:With the current GPU driver, no, but with the new OpenGL driver, yes there is hardware acceleration.Sandros94 wrote:Hi, can you tell me if I'm wrong about chromium (v49 and next coming v50) doesn't have hardware acceleration?
Yeah, I've heard it works for some people but it doesn't for me.Sandros94 wrote:I was reading around that at the moment OpenGL driver are in beta and are too glitchy for a normal use right?kusti8 wrote:With the current GPU driver, no, but with the new OpenGL driver, yes there is hardware acceleration.Sandros94 wrote:Hi, can you tell me if I'm wrong about chromium (v49 and next coming v50) doesn't have hardware acceleration?
