Vivaldi coredumps when starting except --disable-extensions

edwardp

@squeaks Bug reports can be submitted at https://vivaldi.com/bugreport/

Once submitted, you will receive an e-mail at the address you included in the report. Any additional information such as logs and other screenshots can be submitted, by simply attaching them to a reply to the e-mail you received. Sorry to hear of the trouble you are having.

npro

@edwardp said in Vivaldi coredumps when starting except --disable-extensions:

Bug reports can be submitted at https://vivaldi.com/bugreport/

This is of no use at this point. First OP needs to find out which extension is responsible for the crash, then test it again in a clean profile, then post the name of it and the url for others to confirm, then he should report it to the extension author.

squeaks

Ok, I put this at the top because the below may not apply anymore. After singly disabling extensions to find an offender, I retried vivaldi without disabling any extensions expecting coredump fail to start but it started correctly. So it seems if you have the problem I did, running vivaldi with singly each extension you have installed in turn, then running vivaldi without disabling any extensions may fix your problem.

So, then I deleted /Default after all the testing, and copied the failing to start /Default profile back in, and vivaldi now coredumps on start (and writes an 8.8 GB coredump).

[user-arch@antec-arch vivaldi]$ vivaldi-stable 
[95902:95902:0529/143425.093608:ERROR:chrome_browser_cloud_management_controller.cc(162)] Cloud management controller initialization aborted as CBCM is not enabled.
[95941:95941:0529/143428.086479:ERROR:gl_surface_presentation_helper.cc(260)] GetVSyncParametersIfAvailable() failed for 1 times!
[95941:95941:0529/143428.326186:ERROR:gl_surface_presentation_helper.cc(260)] GetVSyncParametersIfAvailable() failed for 2 times!
[95941:95941:0529/143428.332588:ERROR:gl_surface_presentation_helper.cc(260)] GetVSyncParametersIfAvailable() failed for 3 times!
[95902:95902:0529/143434.236723:ERROR:CONSOLE(15)] "Uncaught (in promise) Error: Assertion failed", source: chrome://resources/js/assert_ts.js (15)
[95902:95902:0529/143442.080283:ERROR:CONSOLE(1)] "Refused to create a TrustedTypePolicy named 'dompurify' because it violates the following Content Security Policy directive: "trusted-types ".", source: chrome-extension://mpognobbkildjkofajifpdfhcoklimli/inject-root-bundle.js (1)
Fontconfig error: Cannot load default config file: No such file: (null)
[95902:95902:0529/143456.912263:ERROR:CONSOLE(1)] "Refused to create a TrustedTypePolicy named 'dompurify' because it violates the following Content Security Policy directive: "trusted-types parse-html-subset sanitize-inner-html static-types lottie-worker-script-loader webui-test-script webui-test-html print-preview-plugin-loader polymer-html-literal polymer-template-event-attribute-policy".", source: chrome-extension://mpognobbkildjkofajifpdfhcoklimli/inject-root-bundle.js (1)
[0529/143610.623525:ERROR:elf_dynamic_array_reader.h(64)] tag not found
[0529/143610.623817:ERROR:elf_dynamic_array_reader.h(64)] tag not found
[0529/143610.623947:ERROR:elf_dynamic_array_reader.h(64)] tag not found
[0529/143610.624456:ERROR:elf_dynamic_array_reader.h(64)] tag not found
Segmentation fault (core dumped)

I really don't want to go through singly enabling extensions again to see if the problem goes away, insanity expects a different result. Anyway, this is the rest of my testing procedure:

I deleted my current working profile and copied the crashing profile to ~/.config/vivaldi/Default.
I verified that vivaldi would fail to start and load webpages.

If I run

vivaldi-stable –disable-extensions-except="/home/user-arch/.config/vivaldi/Default/Extensions/jnhgnonknehpejjnehehllkliplmbmhn/1.29.60_0/manifest.json"

an error occurs about being unable to locate the manifest.

Then I ran one by one:


vivaldi-stable –disable-extensions-except="/home/user-arch/.config/vivaldi/Default/Extensions/jnhgnonknehpejjnehehllkliplmbmhn/1.29.60_0/"
vivaldi-stable –disable-extensions-except="/home/user-arch/.config/vivaldi/Default/Extensions/bnomihfieiccainjcjblhegjgglakjdd/4.13_0/"
vivaldi-stable –disable-extensions-except="/home/user-arch/.config/vivaldi/Default/Extensions/hdannnflhlmdablckfkjpleikpphncik/0.0.13_0/"
vivaldi-stable –disable-extensions-except="/home/user-arch/.config/vivaldi/Default/Extensions/ggaabchcecdbomdcnbahdfddfikjmphe/2.12.6_0/"
vivaldi-stable –disable-extensions-except="/home/user-arch/.config/vivaldi/Default/Extensions/aiahkbnnpafepcgnhhecilboebmmolnn/1.0.1_0/"
vivaldi-stable –disable-extensions-except="/home/user-arch/.config/vivaldi/Default/Extensions/bmnlcjabgnpnenekpadlanbbkooimhnj/16.0.1_0/"

In every case, vivaldi starts and is fine except for the vivaldi menu opening causing vivaldi to crash. Tabs open and youtube videos autoplay.

So it becomes a game of maybe a pair of extensions together is causing a crash, or maybe it's not an extension at all.

I did file a bug report.

Below I show some work:

$ cd ~/.config/vivaldi/
[user-arch@antec-arch vivaldi]$ find . -name "manifest.json" -print
./Subresource Filter/Unindexed Rules/9.44.0/manifest.json
./OnDeviceHeadSuggestModel/20230430.530023049.14/manifest.json
./OptimizationHints/393/manifest.json
./FirstPartySetsPreloaded/2023.5.17.1/manifest.json
./WidevineCdm/4.10.2557.0/manifest.json
./FileTypePolicies/58/manifest.json
./SSLErrorAssistant/7/manifest.json
./CertificateRevocation/8021/manifest.json
./PKIMetadata/599/manifest.json
./SafetyTips/2961/manifest.json
./hyphen-data/116.0.5799.0/manifest.json
./OriginTrials/1.0.0.13/manifest.json
./DesktopSharingHub/20220505/manifest.json
./Crowd Deny/2022.12.16.779/manifest.json
./ClientSidePhishing/30.2/manifest.json
./AutofillStates/2020.11.2.164946/manifest.json
./AutofillRegex/2021.8.17.1300/manifest.json
./ZxcvbnData/3/manifest.json
./UrlParamClassifications/2022.11.1.1/manifest.json
./Default/Extensions/hdannnflhlmdablckfkjpleikpphncik/0.0.13_0/manifest.json
./Default/Extensions/jnhgnonknehpejjnehehllkliplmbmhn/1.29.60_0/manifest.json
./Default/Extensions/ggaabchcecdbomdcnbahdfddfikjmphe/2.12.6_0/manifest.json
./Default/Extensions/bnomihfieiccainjcjblhegjgglakjdd/4.13_0/manifest.json
./Default/Extensions/aiahkbnnpafepcgnhhecilboebmmolnn/1.0.1_0/manifest.json
./Default/Extensions/bmnlcjabgnpnenekpadlanbbkooimhnj/16.0.1_0/manifest.json
[user-arch@antec-arch vivaldi]$

npro

@squeaks I see you are on Wayland, Vivaldi does not offer native support for it and is running as an XWayland app. Lots of users have reported issues with Wayland. Try running it with X11 as supposed to. Does it crash then?

If you insist on Wayland I'd say as a further test ditch the command parameters, where you have used a single dash instead of a double dash for ozone-platform=wayland (could be a typo), that double parameter syntax was deprecated iirc for the simple ozone-platform-hint . Go to vivaldi://flags/#ozone-platform-hint and set it there. But again, Vivaldi does not support Wayland as of now.

@squeaks said in Vivaldi coredumps when starting except --disable-extensions:

an error occurs about being unable to locate the manifest.

yes, it's not intended to be used like that, just the path of the directory where it resides, as you did later.

ybjrepnfr

fwiw, though "unofficial", vivaldi has run fine as a full-wayland app in plasma wayland sessions for at least a year'ish, but the latest snappie 6.1.3023.3 broke it [should be irrelevant here though afaict, given o/p is only using stable].

in case any info herein might help the o/p:

thersander

This sounds more or less identical to the thread I've raised at [https://forum.vivaldi.net/topic/87765/vivaldi-has-become-unstable-with-frequent-crashes](link url). Unfortunately I didn't spot this thread before I raised mine.

When starting Vivaldi from the command line, I have even experienced one of the same error messages which you describe, namely:

[0607/175642.253565:ERROR:elf_dynamic_array_reader.h(64)] tag not found

followed by:

Segmentation fault

I have tried repeatedly purging my Vivaldi installation and reinstalling the following Vivaldi versions:

6.0.2979.3-1
6.0.2979.11-1
6.0.2979.15-1
6.0.2979.18-1
6.0.2979.22-1
6.1.3035.51-1

but I now find that I am having crashes irrespective of the Vivaldi version I'm using (currently 6.0.2979.18-1), so I'm not sure if something has been corrupted in my profile by Vivaldi 6.0.2979.25-1, which is the version in use when my crash issues started.

DoctorG

@thersander Does this run in shell?
vivaldi-stable --disable-extensions
if not try:
vivaldi-stable --disable-extensions --disable-gpu

limelemon

Same problem.
At first the situation was exactly as described by squeaks
Then I launched the browser from the console with the command:

vivaldi-stable --disable-extensions

and Vivaldi started successfully.
As mib2berlin advised I moved the current profile to a safe place. After launching Vivaldi, a new profile was created.
I deleted the "Session" directory in the new profile and copied the directory from the saved profile.
Vivaldi starts but crashes on various actions, such as navigating through the browser menu.
The problem persists even though there are no extensions.
The browser crashes on various actions, for example, when navigating through the browser menu.
The error message is always the same:

[0821/002547.289489:ERROR:elf_dynamic_array_reader.h(64)] tag not found

then:

Segmentation fault

About my system:

vivaldi --version
Vivaldi 6.1.3035.302 stable
openSUSE Leap 15.4
KDE Plasma Version: 5.24.4
KDE Frameworks Version: 5.90.0
Qt Version: 5.15.2
Kernel Version: 5.14.21-150400.24.81-default (64-bit)
Graphics Platform: X11
Memory RAM: 32GB

System uses XORG, not Wayland:

loginctl show-session 1 -p Type
Type=x11

Vivaldi kept crashing with no extensions installed.
Then I saved open windows and tabs in two parts in two different sessions.
Now, when you run each of them separately, the browser does not crash.
The extensions are not currently installed.
RAM is sufficient. When all windows and tabs were open at the same time, the computer did not slow down, the browser also worked quickly without any freezes.
Can a large number of simultaneously open tabs and windows together with running extensions be the cause of Vivaldi crash? Synchronization was also performed at the same time.
However, there was no such problem before.
I'm going to test the browser in both saved sessions without extensions, then I'll try to install the extensions again.
What else can be done to solve the problem?

ybjrepnfr

@ybjrepnfr for the interest of those in this thread running v in plasma wayland sessions ... several months ago vivaldi/chromium broke wayland compatibility & would only run as an xwayland app. however, per my recent post, the current snappie is once again running sweetly as a full-wayland app;

https://forum.vivaldi.net/post/688517 | https://forum.vivaldi.net/topic/89678/minor-chromium-update-plus-fixes-vivaldi-browser-snapshot-3105-4/20

limelemon

Testing lasted about two days. During this time, the browser did not crash. Then I turned on synchronization, and all previously installed extensions returned to the browser, as a result, Vivaldi continued to work correctly.
When the number of open tabs reached 576, the browser crashed twice, this was in the form of closing it without error messages. After restart Vivaldi operated normally.

Actions taken:

Launching the browser from the console:

vivaldi-stable --disable-extensions

Creation a session with all tabs.
Transferring the "Default" directory to a safe place.
The restart of the browser and creation a new profile.
Transferring the "Sessions" directory from old profile to new one.
Performing a start of the browser with a previously created session.
The return all extensions that used before.
Outcome: Problem solved.
Thanks to everyone for the advice and help in their posts.