Weird Crashing Bug on Chromium/Vivaldi
-
Hi everyone,
Hoping for some help here on how to troubleshoot/identify a bug.
Vivaldi on Mac Os M1 Max. 6.5.3206.50 (Stable channel) (arm64)
I am going through something crazy on Chromium based browsers - specifically Vivaldi and Google Chrome. I left Chrome to come to Vivaldi thinking the crashes would stop but then realized that its the same base.
I am not even sure how to begin troubleshooting because it is so random. There's no specific action that I do that causes the browser to crash. It could be as simple as a click of a button, changing tabs. It just crashes while being used.
For example, I was on a google meet call and then the rainbow icon shows on the mac and I can't click on any tabs whatsoever but the call keeps running and I can continue to hear people in the conference call.
I feel like this happened about 2 weeks ago with the recent chrome update - maybe it was major? I am sorry, I am a user.
-
Hi,
Welcome to Vivaldi's ForumsStart with the Basic Desktop Troubleshooting Steps.
Extras
- Clean Site Data
- Clean Service Workers
vivaldi://serviceworker-internals/
--
Also,
Some useful links:Forums
Community Official Tutorials Official Help Forum Categories Modding Vivaldi Vivaldi Features Vivaldi Help Forum Markdown Panels • Engines
Vivaldi Tutorials Issues Feature Requests ¿? Menus • Guides • FAQ Vivaldi How To Bug Reports
--
AvoidData loss
Follow the Backup | Reset links below
Vivaldi Backup | Reset + Extra Steps
-
Hi @Zalex108 ,
is there an easier way to perhaps look at the crash logs or something else when it happens?
-
@vivleo said in Weird Crashing Bug on Chromium/Vivaldi:
Hi @Zalex108 ,
is there an easier way to perhaps look at the crash logs or something else when it happens?
Don't know and can't check WinDBG despite it's a Win App.
Maybe @Pathduck knows some way to open a Vivaldi Crash Log. -
@Zalex108 Nope - unless you're a C++ developer there's little useful to get from crash dumps. And if you are a developer, then you (should) already know how to process crash dumps so no point telling you how
(I'm not a developer) -
@Pathduck said in Weird Crashing Bug on Chromium/Vivaldi:
@Zalex108 Nope - unless you're a C++ developer there's little useful to get from crash dumps. And if you are a developer, then you (should) already know how to process crash dumps so no point telling you how
(I'm not a developer)We may ask Gwen @DoctorG whether she knows there's something else
Do you know something to open and look into a Vivaldi's Crash dump file?
-
@Zalex108 said in Weird Crashing Bug on Chromium/Vivaldi:
Do you know something to open and look into a Vivaldi's Crash dump file?
No, i never open such file as i am not developing and debugging for Vivaldi.
-
@DoctorG said in Weird Crashing Bug on Chromium/Vivaldi:
@Zalex108 said in Weird Crashing Bug on Chromium/Vivaldi:
Do you know something to open and look into a Vivaldi's Crash dump file?
No, i never open such file as i am not developing and debugging for Vivaldi.
Thx for the info.
-
@vivleo said in Weird Crashing Bug on Chromium/Vivaldi:
Hi @Zalex108 ,
is there an easier way to perhaps look at the crash logs or something else when it happens?
You may find something here:
https://duckduckgo.com/?q=debug+chrome+.dmp&t=vivaldi&ia=web -
Chrome 120, and Vivaldi 6.5 (with Chromium 120) were released a bit more than a month ago.
Crashdumps are usually not very useful unless you have access the the detailed map information that has been generated for that particular build, and that is only stored internally by the vendors.
If a crashdump was generated it can be uploaded with a bug report (the current snapshots can upload crashdump automatically if enabled).
As you also see this in Chrome, that suggests that it is a general problem in Chromium, and a report should be filed to them as well. (Chrome can also automatically upload crashdumps.)
We are aware of a (possibly) Camera related crash that affects both Chrome and Vivaldi (all known reports are about the crash happening on launch, and involves a deep problem in macOS, not Chromium, upstream is preparing a different implementation, but it can't be backported), but yours does not sound like that issue.
-
@yngve Thank you! I just am stuck and don't know where to start and was hoping that a crashdump could just do it for me or give someone some kind of clue. I guess, I'll just start with the extensions one after another and go from there.