1.14.1077.45 Inspector regularly crashing the entire browser

  • It's driving me INSANE!

    [modedit] shortened title

  • Moderator

    Please calm down, take a deep breath.

    I can tell you: No, not for me.

    What means "regularly crashing"? Every Minute, once a hour, twice a day?
    Explain how i can check it.
    Tell me more about your used extensions.

  • breathe ok, when I say regularly I mean probably roughly every 4th time I open the inspector on average I'd say.

    I have a fair few tabs open over 3 windows and luckily they all open back up okay afterwards, but still very frustrating.

    I'm using it on Windows 10 in case that's relevant, not sure what else might be contributing to it happening...

  • I have been having the same issue for at least a couple months, across multiple versions (public stable and the betas). Every 3rd or 4th time I open the inspector, Vivaldi crashes entirely. No error, just poof, gone. I work in Web Development and Vivaldi suits my work preferences great, but this is a pretty major issue when a major function of a browser causes the browser to crash without even giving any indication as to why.

    Currently I am on version 1.15.1111.3 (x64) on Windows 10. No scripted customizations and very few extensions (uBlock, LastPass, and Hangouts being the main ones). I generally have around 3 tabs pinned and another 2-10 also open, but the crashing occurs whether there are 50 tabs open or 2.

  • Add me to the heap. Used to happen only occasionally, now several times a day. Can't see any kind of pattern whatsoever. Vivaldi is just there one second, gone the next. 1.14.1077.55 (Stable channel) (32-bit) Windows 7.

  • Same issue for me. Please add me to the affected users. I've tried 1.14 32 bit, 1.15 32 and 64 bit as well as 1.16 on 32 bit. all on windows 10.

    Extensions are lastpass, grammarly, react dev tools.

  • Moderator

    I cannot reproduce it.

    If you have no crashes without extension, one of your extensions causes this.
    Try to reset the profile.

    If it does not help please report the issue.
    Please read How to Report a Bug for Vivaldi carefully and then report the bug to Vivaldi bugtracker.

  • Same happens to me all the time!
    @gwen-dragon It is weird that browser developers and other people committed to the project (to Vivaldi, as well as any other browser...) don't test properly.

    Here's how to reproduce the problem on ANY new Vivaldi version (doesn't matter, as this happens since forever):

    • Open 5 browser windows, each having at least 50 tabs, or even 100 tabs (250 - 500 tabs total),
    • Open a new private window with a JavaScript intensive application,
    • Open developer tools in any other window than the private one, but on the tab with JavaScript intensive application.

    The browser will crash, no matter the hardware.

    It is a bug with allocation memory for sure, because it happens even with half the RAM being free (I have 16 GB on one PC, and 32 GB on another one, both 64 bit of course.

    Vivaldi has some serious RAM issues. The browser is super slow with 200 tabs, even when all are hibernated, and only one is active, and there is plenty of RAM. Of course I'm using the 64 bit version of Vivaldi.

    Mod Edit: Sarcasm and flame-bait removed. Please remind yourself of the forum rules. Gwen-Dragon, other volunteers, and the Vivaldi developers can only test thoroughly if a complete recipe is given.

  • Moderator

    @batsk8 said in 1.14.1077.45 Inspector regularly crashing the entire browser:

    @gwen-dragon It is weird that browser developers and other people committed to the project (to Vivaldi, as well as any other browser...) don't test properly.

    Calm down, be friendly if you want help!
    Give us more information about your crashes and we may investigate.
    We need a real test case and not a vague description.
    We need crash dumps.
    I can not see that you had reported your bug.

  • Apologies for the lack of information in my initial post, I had reached my wits end with this crashing and I'm still suffering with it now a few updates later.

    As stated by others it seems to happen very randomly, but for me it's at least daily and regardless of the situation so I'm afraid I've not been able to narrow it down very much.

    I've only got 2 extensions, AdBlockPlus and Eye Dropper, is anyone else seeing this issue with neither of these extensions?

  • So I have done a bit more observation on his problem, which affects me on 1.14, 1.15 and 1.16 on Windows 10.

    This used to happen regularly when I was testing a software where I needed to test on two different accounts ie. was using a private browser regularly. I've now used a different browser for that portion of my testing have have not had any more crashes since.

  • This exactly have been happening for me for long time already, glad I'm not alone. This is very frustrating, since I'm developer and 90% of the time I use devtools. I don't want to reset my profile just to test this bug, because I've been using browser for long time and spent time configuring it. I use stable channel and I expect browser not to crash at all. Is there a way, maybe, to temporary start vivaldi with new profile and come back to existing state after testing?

    Vivaldi 1.15.1147.42 (Stable channel) (64-bit)
    Revision e6c78ca75e5f4970771b2c6e6727bb07c4a76464-
    OS Linux
    Flash /usr/lib/adobe-flashplugin/libpepflashplayer.so
    User Agent Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/65.0.3325.183 Safari/537.36 Vivaldi/1.96.1147.42
    Command Line /usr/bin/vivaldi-stable --flag-switches-begin --enable-gpu-rasterization --ignore-gpu-blacklist --flag-switches-end

    Extensions uBlock origin, Privacy Badger, Surfingkeys. (anybody use same extensions have crashes?)

  • Moderator

    If you see such crashes, please send us the crashdumps (the ones with timestamp around the time of crash.

  • Finally this stopped happening on version 1.15.1147.47. Thanks to devs.

  • Moderator

    Closed as resolved in 1.15.


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