4.0.2312.24 crashes on ElCapitan 10.11.6
-
The dev has fixed the issue internally, but it might take some time to reach the Stable version. Hopefully, it'll be in the next Minor Update, but I can't make any promises.
-
@jane-n That'd be great, really. And it would be nice, also, if anyone out there could somehow "confirm" that moving forward will not pose any problems as far as El Capitan users is concerned. I am not willing to go through the same ordeal again.
-
@jane-n Thanks for the hope, anyway
-
@carlos66ob said in 4.0.2312.24 crashes on ElCapitan 10.11.6:
@jane-n That'd be great, really. And it would be nice, also, if anyone out there could somehow "confirm" that moving forward will not pose any problems as far as El Capitan users is concerned. I am not willing to go through the same ordeal again.
@carlos66ob I don't think it was an OS version issue. I think it was a quality check failure. It could have been with the latest OS. That @jane-n will not say more than comment about possibility of when the fix will reach us, is not helpful either. I suppose, however, that almost two weeks later, some information from them is better than none. So we wait.
-
Hi, folks. Sorry for not staying on top of issues here. However, I'll try to give you an update as to what's going on with this crash.
First, a number of you submitted bug reports and crash logs. Thank you for that! I don't have access to a symbolicated crash log, so I can't see exactly where in the code that the crash occurred... but it looks like it was related to some changes that were made in conjunction with the Chromium 91 uplift. That has been fixed internally. (Apparently, we don't have many Snapshot testers running macOS 10.11.6 or else this crash would have discovered and fixed much earlier.)
Following the crash fix, the team did some addition testing and found some other issues related to proprietary media playback. A fix is in the works for that issue as well.
Ideally, it would be nice ship an update with both fixes. Given that this is a crash, there is urgency to get this resolved as soon as possible... HOWEVER... they also would not want to ship a fix that might introduce instability in Vivaldi running on more current versions of macOS.
-
@xyzzy
I had tested Vivaldi.4.0.2312.27.universal.dmg on MBP 15" late 2008 and MB 13" (white) early 2009. Both use ElCapitan (the latest running on this hardware without hack). On both Vivaldi crashes at starting. I only see a empty frame for a short time.
Of both I had send you the crash log as text file! -
@fredonmac said in 4.0.2312.24 crashes on ElCapitan 10.11.6:
@xyzzy
I had tested Vivaldi.4.0.2312.27.universal.dmg on MBP 15" late 2008 and MB 13" (white) early 2009. Both use ElCapitan (the latest running on this hardware without hack). On both Vivaldi crashes at starting. I only see a empty frame for a short time.
Of both I had send you the crash log as text file!@fredonmac, yes I can confirm as well. I shut the browser down yesterday and this morning it will not start. I had to completely remove it, as described earlier, and reinstall the old version. Perhaps @xyzzy can pass the word so that they can ensure that it does NOT auto update, ever. It's already a memory hog, Each time I shut it off, I reclaim about 2gb of hard drive space. I don't want to leave it running all the time. And I don't want to spend time uninstalling and reinstalling every morning, simply to use a browser. Perhaps it's time I move on. @xyzzy explanation that they don't have "many Snapshot testers running macOS 10.11.6" is funny. Why release for a platform if you cannot, or have not tested? When you consider the time this has taken, and consider the silence for a week, it's well past disappointing.
-
@bnmnesta
On the old Macs with ElCapitan, there are no security updates for long times ago, specially Apple WebKit is very old.
So I must use an browser without WebKit. Firefox don't use WebKit and is my main browser.
I don't know where the WebKit versions from the different browser coming - from Apple or from the browsers self.This browser I have installed for test now:
Firefox 78.11.0esr (64-Bit) [the latest version that running on ElCaptan]
Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:78.0) Gecko/20100101 Firefox/78.0Safari 11.1.2 (11605.3.8.1) [the latest version that running on ElCaptan]
Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_6) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/11.1.2 Safari/605.1.15Vivaldi 3.8.2259.42 (Stable channel) (x86_64) [the latest version that running on ElCaptan]
Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/90.0.4430.214 Safari/537.36Brave Version 1.25.73 Chromium: 91.0.4472.106 (Offizieller Build) (x86_64)
Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/91.0.4472.106 Safari/537.36Opera Version:77.0.4054.90 (x86_64)
Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/91.0.4472.77 Safari/537.36 OPR/77.0.4054.60iCab 5.9.2 [the latest version that running on ElCaptan]
Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_6) AppleWebKit/601.7.8 (KHTML, like Gecko) iCab/5.9.2 Safari/604.5.6For version test I use this php script on an web. If anyone have a better script, please let me know.
<?php echo "<u>Your HTTP USER AGENT:</u> ". $_SERVER['HTTP_USER_AGENT']; ?> -
@fredonmac The User Agent string is reported by the browser itself: https://developer.chrome.com/docs/multidevice/user-agent/
I'm not certain of the significance of AppleWebKit/537.36; that might have been the version that the Chromium team forked when they created Blink.
I don't know where the WebKit versions from the different browser coming - from Apple or from the browsers self
-
@bnmnesta FYI, the Vivaldi team is working on getting a fix out ASAP; hopefully VERY soon.
Perhaps it's time I move on. @xyzzy explanation that they don't have "many Snapshot testers running macOS 10.11.6" is funny. Why release for a platform if you cannot, or have not tested? When you consider the time this has taken, and consider the silence for a week, it's well past disappointing.
Your frustration is understandable. I also don't recall this sort of thing ever happening before... and I also used to have a Mac that I couldn't update past 10.11.6 as well. I also hope that the Vivaldi team can continue to support older Macs. However, there will come a day when either the Chromium team will raise their minimum system requirements or it will be impossible to develop software for the newest versions of macOS and still maintain compatibility with older systems.
-
FYI, the Vivaldi team has released an update that should fix this crash: https://vivaldi.com/blog/desktop/minor-update-3-for-vivaldi-desktop-browser-4-0/
-
@xyzzy yes, working now (4.0.2312.33). thanks
-
Now it works well
Vivaldi 4.0.2312.33 (Stable channel) (x86_64)
Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/91.0.4472.114 Safari/537.36Thanks Vivaldi!
--
Nice Greetings
Fritz -
@xyzzy Seeing how the computer world works today, I understand that in the end they stop giving support. But the logical thing would be to mention it on the front page: "from this version 4 the X, Y, Z systems do not work ... and the requirements are these".
And of course, the most important thing: mention those same requirements both on the main page and on the download page. In aid. Everywhere. And do not do as many: assume that everyone uses the latest version, whatever it is. Or limit the help to "update, update, update ...".
And never mention from which versions it works or that other feature. Or system. Before, at least it was said: "from version 2 you can use iCloud, from 3 iCloudDrive, and from 4 SuperICloud2000"
Now everyone assumes that you use the latest of the latest, and that tomorrow it will be obsolete. Even just for 24 hours. And they don't even accept that this is not the case. Nor do they care the least for those who don't. They do not exist. -
too much hate from some people to devs who do their job. guys, nobody owes you a thing, relax, be thankful for prompt fix and support of old OS, most of the devs in other software projects just give up and drop support of elcap
-
@cisebo6015 I my view, this is not about hate but to being properly informed. Devs do their job, a good one, indeed. However, as @MacTerrasa points out, we deserve at least to know if and why some given update is not going to work anymore with our systems; if there will be some other working in the future or they are dropping support for good. Nobody owes us nothing and hating is out of the question, but some kind of respect always helps.
-
@fredonmac Is that so?
-
@xyzzy said in 4.0.2312.24 crashes on ElCapitan 10.11.6:
FYI, the Vivaldi team has released an update that should fix this crash: https://vivaldi.com/blog/desktop/minor-update-3-for-vivaldi-desktop-browser-4-0/
@xyzzy thanks. but no support for 'propriety media' can you say what this means, even an example or two would do.
-
@bnmnesta 'Proprietary media' refers to Vivaldi's support for patent-encumbered codecs, such as H.264/AVC. These media types are special in that they are decoded using codecs that are part of macOS. Vivaldi users running on El Capitan will still be able to play most videos on YouTube but will run into playback issues on sites such as Twitter, Vimeo, etc. until a fix gets released, which hopefully will be included in the next 4.0-Stable update.
-
@carlos66ob Yes, it seems that .33 works fine, finally, in ElCapitan. Thanks!
-
Ppafflick unlocked this topic on -
Ppafflick moved this topic from Vivaldi for macOS on
