This browser I have installed for test now:įirefox 78.11.0esr (64-Bit) I don't know where the WebKit versions from the different browser coming - from Apple or from the browsers self. Firefox don't use WebKit and is my main browser. 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 the old Macs with ElCapitan, there are no security updates for long times ago, specially Apple WebKit is very old. explanation that they don't have "many Snapshot testers running macOS 10.11.6" is funny. And I don't want to spend time uninstalling and reinstalling every morning, simply to use a browser. I don't want to leave it running all the time. It's already a memory hog, Each time I shut it off, I reclaim about 2gb of hard drive space. Perhaps can pass the word so that they can ensure that it does NOT auto update, ever. I had to completely remove it, as described earlier, and reinstall the old version. I shut the browser down yesterday and this morning it will not start. Of both I had send you the crash log as text yes I can confirm as well. I only see a empty frame for a short time. Both use ElCapitan (the latest running on this hardware without hack). 24 crashes on ElCapitan had tested Vivaldi.27.universal.dmg on MBP 15" late 2008 and MB 13" (white) early 2009. they also would not want to ship a fix that might introduce instability in Vivaldi running on more current versions of said in. Given that this is a crash, there is urgency to get this resolved as soon as possible. Ideally, it would be nice ship an update with both fixes. A fix is in the works for that issue as well. (Apparently, we don't have many Snapshot testers running macOS 10.11.6 or else this crash would have discovered and fixed much earlier.)įollowing the crash fix, the team did some addition testing and found some other issues related to proprietary media playback. but it looks like it was related to some changes that were made in conjunction with the Chromium 91 uplift. 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.
However, I'll try to give you an update as to what's going on with this crash.įirst, a number of you submitted bug reports and crash logs. Sorry for not staying on top of issues here.
0 kommentar(er)
