Vivaldi crashes after closing another window with a single non-empty tab.

  • Vivaldi crashes when I close another window with a single non-empty tab. I can reproduce this easily:

    • I start Vivaldi normally
    • I open a new Vivaldi window
    • I open any site in the only tab
    • If I close that window, Vivaldi closes all the windows that were open, not just the window I tried to close.

    To avoid this, I have to close the new window with the speed dial in the only tab or close the new window with more than one tab.

    Can anyone confirm this?

  • @akira_kazama This is a very annoying bug when I'm working with sessions or private windows but no one seems to care.

  • Hi, cant reproduce on my system.

    Opensuse Leap 42.1 x86_64
    CPU Intel T4200 4 GB
    GPU Intel GN 965
    xf86-video-intel 2.99.917-6.1
    KDE Plasma 5.8.7
    Vivaldi latest snapshot

    Cheers, mib

  • @mib2berlin Thanks for trying, I forgot to mention that I use the latest stable version. Vivaldi 1.13.1008.34 (Stable channel) (64 bits) and Linux Mint 18.3 64-bit

  • Moderator

    @akira_kazama Can't reproduce here with Mint 18 64-bit and Vivaldi 1.13.1008.34

  • @ayespy Running Vivaldi from a terminal I have found that it closes due to a segmentation fault. How would I know what is causing this problem? 😞

  • Moderator

    @akira_kazama I'm not technically sophisticated enough to answer that. Sorry.

  • @akira_kazama
    Do you load a page in the first window before you open the second?
    May you can make a screen cast.

    Cheers, mib

  • @mib2berlin Yes, I have some pinned tabs in the first window but I also have tried closing them all leaving just the speed dial tab and Vivaldi still crashes after closing the second window. I have disabled all the extensions with the same result.

    It seems I will have to create a new profile folder because Vivaldi broke something with this update.

  • I'm having similar crashes. They happen when I'm using CA USD Service Desk and some javascript calls an action of "close window", then the entire browser suddenly closes.

    Linux Mint 18.1 Cinnamon 64-bit

  • Nevermind, I pinned the tabs as you guys said and now it's working. Thanks!

  • Okay, I give up. Today I have restarted my profile following these instructions: but Vivaldi still kept crashing due to segmentation faults.

    My solution was to reinstall Vivaldi 1.12 and block the update to this unstable version, now everything works perfectly.

  • Moderator

    @akira_kazama said in Vivaldi crashes after closing another window with a single non-empty tab.:

    but Vivaldi still kept crashing due to segmentation faults.

    Please report the crash!

    How to do a bug report for Vivaldi

    Report each bug separately at
    Describe the issue as precise as you can.
    Add some information about extensions you use.
    Add information about the operating system and version you use.
    Add some information which security tools you use.
    If you have problems with video or audio give us information about your installed codecs and graphics
    Add a exact link to the page where the issue comes up and can be tested.
    After reporting the issue, you will receive a confirmation mail from the bugtracker.
    In a reply to this mail you can add more information and files (like screenshots or testcases) as
    attachments and it will be added automatically to bug report.

    If you have questions about the bug please ask in forum first and do not forget to post the VB-XXXXX
    bug number (you can find it in confirmation mail).

    Thanks in advance for helping us to make Vivaldi better!

  • @gwen-dragon This bug has been fixed in the latest stable build (VB-35340).

    Thank you very much for your help.

  • FYI: Still happens. No extensions. Have two windows. Have tabs open in each. Close or move tabs in second window until you get to last one. Move that last tab to the other window - both windows crash. Restart, and both windows open. Then you can move the last tab from the second window to the first window.

    Vivaldi 1.15.1147.36 (Stable channel) (32-bit)
    Revision 166efd59c7aba158f456fc82eabf5d0dffdc41f5-
    OS Windows
    JavaScript V8
    Flash C:\WINDOWS\SysWOW64\Macromed\Flash\pepflashplayer32_29_0_0_113.dll
    User Agent Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/65.0.3325.183 Safari/537.36 Vivaldi/1.96.1147.36
    Command Line "C:\Users\Bewc\AppData\Local\Vivaldi\Application\vivaldi.exe" --ppapi-flash-path="C:\WINDOWS\SysWOW64\Macromed\Flash\pepflashplayer32_29_0_0_113.dll" --flag-switches-begin --site-per-process --flag-switches-end
    Executable Path C:\Users\Bewc\AppData\Local\Vivaldi\Application\vivaldi.exe
    Profile Path C:\Users\Bewc\AppData\Local\Vivaldi\User Data\Default
    Compiler clang

  • This bug was fixed but now it happens again, it seems this is a regression.

  • Yes, very annoying, and happens very often.

    I'm not sure it is the same issue than the original post of this thread, though. It does not seem to be a segmentation fault.
    By starting VIvaldi from terminal, the message on crash is:

    Instruction non permise

    which means:

    Forbidden instruction

    Moreover, the syslog (/var/log/syslog) shows an entry referring to "trap invalid opcode":

    kernel: [263212.851490] traps: vivaldi-bin[16131] trap invalid opcode ip:564747d0255e sp:7fffc7f04c00 error:0 in vivaldi-bin[5647472e1000+5bd9000]

    Is it the same thing for you?
    I haven't tested the last snapshot (1.16.1195.3) but there is nothing refering to this bug in the changelog.

  • @guilimote You are right, this time Vivaldi crashes due to a "Illegal instruction" not a segmentation fault.

    I hope this will be fixed too.

  • Moderator

    Please report new crash bugs!

    Please read How to Report a bug for Vivaldi carefully and then report the bug to Vivaldi bugtracker.

  • @gwen-dragon already done a couple of weeks ago.

    But as always, closed tracker means that we are totally blind about what happens to the issues, so I prefer raising it on the forums too when I see it affects other people.

    When I reported it, I thought it was related to private windows (VB-40052, hence the issue title), but I answered back the tracker mail a few days ago to give more info and explain it is not limited to this use case.


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