1.14.1077.45 was rushed out without fixing the bugs

  • IPvfoo no access to address bar, no drop down in address bar while typing, these bugs should be fixed before the final. On my other desktop there is no drop down working inside the address bar.

    [modedit] added version

  • Enable address bar autocomplete, it's a workaround, and yes, the rush to release the chromium 64 update really caused a ton of small regressions, but they sum up to a very annoying experience.

  • Moderator

    Do not forget the serious security fixes in Chromium 64! Thats one of many facts we had to get it out to users.

  • @gwen-dragon with all the due respect, i don't give a damn if i get a broken browser.

  • First Vivaldi can't recognize the program to open protocols now the protocols don't even work.

    magnet: broken, steam: broken... 😒

  • On 1.14.1077.41 I'm suddenly seeing Twitter broken. Investigating cause.

    EDIT: Only on Windows. Working on Mac.
    EDIT 2: all browser keyboard shortcuts also appear to be nonfunctional on all twitter.com pages
    EDIT 3: traced to "Twitter Disconnect" extension, which I'd missed disabling (and whose functionality I have via other extensions).

  • I'm sorry to say, but i agree with the title & sentiment of this thread.

    In https://vivaldi.com/blog/snapshots/vivaldi-1-14-rc-2/ i wrote:

    VB-36600 -- still a problem in 1.14.1077.37 and 1.14.1077.39 [ie, updating Linux V-SS SD TNs still crashes V].

    Surely you can't really release Stable when this continues to occur?

    Now that 1.14 Stable has been released, without VB-36600 being fixed, i was curious to see if the bug was now also present here [I expected the answer to be yes]. I launched the new 1.14 Stable, displayed a SD page, pressed F5, & after ~1 minute, as i had anticipated, it crashed... just like in SS. My 1.13 Stable did not crash, ie, prior to the 1.14 update.

    Most of us using Snapshots know & accept that it will have bugs, but IMO it's not at all a good look to release known unsolved bugs that crash Vivaldi, into new so-called Stable releases. Non-Vivaldi aficionados, ie, Joanna Public, could be excused for being shocked if their self-called "Stable" browser crashes just by vanilla actions like updating speeddial thumbnails.

  • just to add some fuel to the fire, I've just updated 2 of mine bug reports,

    (VB-36485) regression: magnet links don't work anymore from this snapshot
    Just to update, it's still a problem in 1.14.1077.41 (Stable channel)
    many URI are affected:
    The regression is here after 1.14.1064.3, which is the last working version.

    (VB-36537) Downloading large files from mega.nz crash Vivaldi
    The problem is still there, downloading anything large (100/200 + Mb) from mega.nz, with or without the mega extension, Vivaldi brutally crashes.
    And this from 1.14.1072.3

  • @rluik

    +1 Reported a similar bug

    Vivaldi 1.14.1077.41 (Stable channel) (32-bit)

    Devastates applications that rely on this integration (eg: webvpn).


  • I can confirm the same thing using the screenconnect service. v1.13 works and prompts the below screen, however, 1.14 never prompts for anything and never opens the client. I had to re-download the client multiple times until i regressed to 1.13 to see if that fixed the problem, it did.


  • Please work on fixing the bugs now.

  • Moderator

    @saudiqbal Do you really need to keep repeating this mantra? They are always working on fixing bugs.

  • Moderator

    @saudiqbal Work is full steam ahead to fix 1.14 bugs. I don't know, but it would not surprise me in the slightest to see a bugfix minor update for 1.14. Unfortunately, it could not be held back any longer as to release date, but bugs are receiving full attention.

  • @gwen-dragon By serious, I guess you mean the Spectre ones. Those were backported to 1.13, right?

  • @pesala said in 1.14 was rushed out without fixing the bugs:

    @saudiqbal Do you really need to keep repeating this mantra? They are always working on fixing bugs.

    The point here is not that they They are not working on fixing bugs. The point is they have released browser that shouldn't be released as STABLE!!!! release given to all those who trust to the built in update tool in browser. It is far too buggy.

    I lost 3 days only to solve the problems with 1.14, reporting bugs, trying to revert back to 1.13 and so on. I have also lost system and data from half month because of unfortunate series of accidents (Windows 7 restoration led to BSOD instead of restoration) triggered by this shi.y version . Of course not a direct fault of Vivaldi bugs just a trigger, but please think how many people get upset, has lost their time or something else just bacause of the premature v1.14. I only can imagine how many people has probably forever drove away from Vivaldi.

    And was it worth to hurry so much? Tell me what a wonderfull things are in 1.14 which 1.13 has not. And even if they were, these wonders accompanied by so many bugs, it should be released as some beta version not as fully working tool for everyone.

    I've lost my trust to Vivaldi so much a has switched off update notifications. It would take a lot of time to even consider any update of Vivaldi and for sure it will follow spending a lot of time on reading forums.

  • Moderator

    @ksus The release schedule of Vivaldi is so severely dictated by Chromium, that they cannot simply keep withholding stable releases because Chromium is breaking things. They fix everything they can and then sooner or later they have to release. 1.13 was based on Chromium 62. 1.14 was based on Chromium 63. Chromium 63 broke so much stuff that no stable release was ever possible using it, and the decision was made to release 1.14 on top of Chromium 64. Even so, having skipped an entire Chromium release without a new Vivaldi stable release, the team was a bit late getting 1.14 out the door. Everything that was exposed in user feedback, and which could reasonably be addressed, was taken care of before the 1.14 release. Nonetheless, there were about 3 fairly important (to some people; they never appear in my usage patterns) bugs that either could not be fixed or were not exposed to the developers before release - and one of these is a Chromium bug which Vivaldi is not eligible to address. Chromium has to do it. The other two are sufficiently important that it would not surprise me at all to see Vivaldi come out with a bugfix minor update for 1.14 while 1.15 development moves forward.

  • That's still a bit of a weak excuse. I understand that there was a new Chromium release, but that by no means requires an immediate RTM of Vivaldi 1.14 or necessarily an RC. Vivaldi 1.14 RC1 dropped Jan28, followed by RC2 Jan29, and "Stable" Jan30. I wouldn't be surprised if many snapshot users weren't even aware RC1 released by the time RC2 and 1.14 "Stable" were released. The published changelog for RC2 reflects 1 bugfix over RC1.

    Opera Stable is at version 50 (using Chromium 63) and they only just released their first RC for version 51 using Chromium 64 yesterday. If Opera is behind Vivaldi pushing a Chromium 64 release, it seems Vivaldi might have been capable of delaying a little longer to iron some things out. It's almost as if there was a deadline to release a final version using Chromium 64 before Opera.

    Magnet links being broken is perfectly understandable as that's an issue with Chromium 64. However the address bar drop down menu is something that rests solely on the shoulders of the Vivaldi devs; It was introduced in snapshot 1.14.1030.3 and is probably related in some way with VB-34967 which was fixed in the following 1.14.1036.3 snapshot two months ago. Clearly this particular regression isn't a showstopper and many won't notice it but it severely hinders productivity for many people.

    Unfortunately the issues myself and others have experienced with Vivaldi 1.14 hanging, crashing, and putting an obnoxious load on CPU and RAM while doing so render it unusable forcing me to downgrade to 1.13. That is a showstopper and they're issues which could have been raised sooner...

    Just seems like quality keeps taking a backseat.
    @ayespy said:

    Nonetheless, there were about 3 fairly important (to some people; they never appear in my usage patterns) bugs that either could not be fixed or were not exposed to the developers before release - and one of these is a Chromium bug which Vivaldi is not eligible to address. Chromium has to do it. The other two are sufficiently important that it would not surprise me at all to see Vivaldi come out with a bugfix minor update for 1.14 while 1.15 development moves forward.

    May I ask what the other two are?

  • @hekel I agree, fairly easily reproducible runaway RAM and CPU issues trumps any urgency for a new build with a new Chromium, especially since the precedent was made recently in backporting notable security fixes into 1.13.

    Delaying a release, or even skipping a major Chromium version (as I'm sure will happen again, since it's impossible to keep up over the long run), are not problems that compare to the sorts of things seen in 1.14.

  • It's sad to see Vivaldi's priorities. They rush out a release with markdown on notes as one of the only highlights and break basic stuff like protocol handlers and a lot of extensions, something I discovered because the ad-blocker I use didn't want to unblock the exceptions I put in the filter.

    This contradicts their own post about Snapshot vs Stable version where they write "Current features can also break in a Snapshot (the so-called regressions)". With regressions slipping into Stable there's no difference and one might as well use the snapshots as daily driver.

    The unfortunate truth is I'm still unable to recommend Vivaldi unless the person is a masochist that wants to deal with issues.

  • Moderator

    With any software, not just Vivaldi, a decision needs to be made whether or not to release. Every six weeks, the Chrome/Chromium team (pretty much always) makes the decision to release because it's deemed more important to release on schedule (and not delay 40 security fixes) than it is to fix the remaining "release blocker" bugs. In this particular cycle, Chrome 64 was rushed out with even more urgency in order to also mitigate two high-profile CPU bugs (Spectre and Meltdown) that were severe enough to merit their own logos, t-shirts, hashtags, twitter handles, and web sites.

    Vivaldi makes every effort to fix critical bugs during the Snapshot stage. It's really easy to criticize Vivaldi but remember that once Chrome gets released, the next major Chrome release will be out (ready or not) in another six weeks. During that time, Vivaldi has to get their Stable release out, integrate (still buggy) Chromium beta code into a Snapshot, release follow-up Stable releases containing the latest Chromium fixes and their own fixes, and get the next Vivaldi snapshot (containing new features, enhancements and additional bug fixes) ready enough to test, and have a release candidate ready before the madness starts all over again.

    With that in mind, I have nothing but the utmost respect for the entire Vivaldi team.


Looks like your connection to Vivaldi Forum was lost, please wait while we try to reconnect.