Solved Browser keeps closing / crashing on its own
-
@xyzzy Admonition about "Downgrading" understood. I tried it for about 24 hours (reliving the fond memories of a working Vivaldi), and went back to Firefox (with Sidebery for the Vivaldi-like interface) until the new update that finally works. Thanks.
-
@nickoo "Security risk" understood. I tried 5.1 for only 24 hours until the new update that works, finally.
-
@lillianli New update works--note the warnings here about security when using older versions.
-
@davinci42 Snapshot users will see a fix for this when the next build gets released.
bcos it's kinda a very serious bug, hope we can release for it as well.
not pushing you guys, but there're many people use Snapshot version to test new features and report feedback to make Vivaldi better.Yes, it an important fix. However, Snapshot builds are provided to allow users to test new features, that are under development, before they get released broadly to the Stable channel. Normally, Snapshots are the first to receive fixes and new features. However, Snapshot build updates can also get put on hold when ongoing work is either not ready-enough to release or when Internal testers report serious regressions or stability issues.
As an Internal tester, on Mac, I have Stable and Snapshot builds installed side-by-side. (On my Windows system, I have Stable installed system-wide and have Snapshot installed "standalone".) I can do all my day-to-day work on either, and I will switch between which installation I use primarily depending on the circumstance or whichever one is the most stable for me at the time.
-
The new update didn't fix the problem on my work computer. It seems fine on my home laptop, but my mac pro at work has crashed twice already today after I installed the update. What's going on?
-
I've never been able to get Vivaldi 5 to run without crashing, so I've been using Vivaldi 4 all along. This week, I updated to Monterey, removed Vivaldi.app (v4) and the Vivaldi folder in ~/Library/Application Support, and installed Vivaldi 5 -- 5.2.2623.48 (Stable channel) (x86_64). I didn't install any extensions. With only 6 tabs open, I visited https://opensource.com/article/20/4/plot-data-python and Vivaldi crashed (after not responding for about ten seconds). When I looked for the crash file, I got this response in the terminal:
find ~/Library/Logs/DiagnosticReports -mtime -7 -name Vivaldi\*.crash | zip -j ~/Documents/Vivaldi\ Crash\ Logs\ $(date '+%Y%m%d-%H:%M') -@ zip error: Nothing to do! (/Users/bburd/Documents/Vivaldi Crash Logs 20220519-16:53.zip)
Using the Finder, I found no file containing the name Vivaldi in ~/Library/Logs/DiagnosticReports folder.
I reopened Vivaldi and saw that the offending tab wasn't loaded. (All other tabs were loaded as they were before the crash.) I visited https://opensource.com/article/20/4/plot-data-python again and, again, Vivaldi crashed. I've tried the experiment several time since then, and that page always makes Vivaldi crash. That page also makes Chrome crash, but the page doesn't crash when I open it in FireFox.
What can I do to diagnose this problem? -
Touch wood, Vivaldi 5.2 has been stable for a while. It seemed to get better BEFORE the recent update, which I find slightly odd.
-
This post is deleted! -
The issue is still there. It seems less often (although hard to tell since it's very random). Most of the time, it happens when I'm working on Google Sheets if that helps.
-
@bburd Are you running macOS 12 Monterey? That version generates .ips files, not .crash files. I have asked the Vivaldi team to update the reporting-crashes-on-macos help page.
You can also check for crash logs by launching Console.app and selecting Crash Reports.
-
Ok so just had Vivaldi crashing several times in a row again...
Vivaldi 5.2.2623.48 (Stable channel) (arm64)
Revision 80d94afbd301a973f33b94e8c76a22a33ed078c7
OS macOS Version 12.4 (Build 21F79)
JavaScript V8 10.0.139.17
User Agent Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/100.0.4896.162 Safari/537.36
Command Line /Applications/Vivaldi.app/Contents/MacOS/Vivaldi --flag-switches-begin --flag-switches-end --disable-smooth-scrolling --save-page-as-mhtml
Executable Path /Applications/Vivaldi.app/Contents/MacOS/Vivaldi
Profile Path /Users/erwanmenais/Library/Application Support/Vivaldi/Default
Linker lldI don't find any crash logs in the console.app
-
I have Vivaldi set to reopen the tabs that were open when it last closed. But now, because of a tab that crashed Vivaldi, I can't open Vivaldi without it's crashing. Is there a way to edit the tabs that will open by tinkering with the files in the Default profile? That would help a lot.
-
@bburd The easier thing to try first is to disconnect your computer from the network/Wi-Fi and then launch Vivaldi. If you don't get a crash, you can then start closing tabs that you suspect may be triggering the crash before you reconnect to the network again.
I have Vivaldi set to reopen the tabs that were open when it last closed. But now, because of a tab that crashed Vivaldi, I can't open Vivaldi without it's crashing. Is there a way to edit the tabs that will open by tinkering with the files in the Default profile? That would help a lot.
-
In my case, 5.2.2623.48 fixes the problem. No crashes in several days. (MacOS 10.14 and 10.15)
-
5.2.2623.48 still does not work for me, had a crash after <5 minutes of using Vivaldi after confirming update, and I'm pretty sure it happened before that as well.
Monterey 12.2.1, 2021 MacBook Air.
-
I can confirm the problem still exists. Not very often but Vivaldi still crashes 1 or 2 per a day.
-
Had 5 successive crashes tonight, following mem past 10GB & temp above 170 F... Re-starts; finally resorted to (already) running snapshot -- which crashed in a few minutes time!
Computer is now "dreaming" comfortably -- w/o electrical "complications...(What, me worry?:)
-
For me, it's even worse than before the update since now when it crashes it doesn't save the crashed session so I can't even open the tabs that were closed.
I guess that's it for me, gonna look for a new web browser today. Really a shame because besides the crashing, I genuinely love Vivaldi. -
I have not experienced any browser crashes following the latest fixes on Vivaldi 5.2 Stable and 5.3 Snapshot.
For any of you who are still seeing crashes, did you ever revert back to an older release? I know, from my own personal experience and testing, that this can cause irreparable damage to your Vivaldi installation and the resulting instability can also cause Vivaldi to crash. If this is the case, you may need to either clean your profile or possibly even reset Vivaldi back to a new/clean state.
-
@xyzzy No, I never downgrade to avoid those issues. I was dealing with the issue just waiting for a new version to fix it.