To report a crash on Linux, create a bug report on Vivaldi.com/bugreport and describe the crash. Especially useful are detailed steps that we can follow in order to reproduce the bug on our side. Make sure to give a valid contact email we can reach you on, as we may need more information or ask you to perform some tests for us, to help us better understand the issue.
Capturing a crashlog
If you are an advanced user, who feels comfortable with the command line, then you might want to attempt to capture a backtrace (crash log). This greatly assists the developers in understanding an issue. Particularly if we cannot reproduce it ourselves. This backtrace can then be attached to your bug, by replying to the email we sent you after you first logged the issue. To capture a backtrace you will first need to install a debug binary.
Install a debug binary
- Go to “
vivaldi://about” and note architecture listed within the “User Agent” section (i.e. x86_64, i686, armv7l or aarch64).
- Download a suitable Vivaldi debug binary (adjust the architecture if needed):
- Uncompress the debug binary:
gzip -dS.zip vivaldi-latest-x86_64-debug.zip
- Install the debug binary:
sudo install -m755 $(ls -t vivaldi*debug | head -1) /opt/vivaldi/vivaldi-debug
Recording a backtrace for a full UI crash
To capture a crash in our UI (full browser crash) issue the following in a terminal window to start Vivaldi under the GDB (GNU Project Debugger)
gdb -ex run --args /opt/vivaldi/vivaldi-debug
Now repeat the procedure that you usually use to crash the browser. Once Vivaldi has crashed you can issue the following in the GDB console to obtain a backtrace of the crash
Copy the entire backtrace to your clipboard and send it along to us as a reply to the email we sent you after logging your bug report.
To exit GDB issue the following:
vivaldi://about” to find this), change all references of “
/opt/vivaldi/” to “
/opt/vivaldi-snaphot/” and add “
--user-data-dir="$HOME/.config/vivaldi-snapshot"” to the end of the gdb launch command.
Recording a backtrace for a tab crash
If however, you are an advanced, technical user, understand the ramifications of disabling the sandbox and wish to continue, we would certainly appreciate a crashlog created via the following method.
Since we will be spawning a terminal in a new window for every renderer process (including every tab), it is strongly recommended that you close all but the essential tabs in your session before you begin. Now issue the following to start Vivaldi:
/opt/vivaldi/vivaldi-debug --no-sandbox --renderer-cmd-prefix='xterm -title renderer -e gdb -ex run --args'
Bring the tab you wish to crash to the foreground and complete any steps to invoke the crash. When the crash happens, you will not see the normal “dead bird” picture associated with a tab crash. Instead that tab will simply freeze and become unresponsive. One of the terminal windows (associated with the crashed tab) will now display something like the following:
Thread X "vivaldi-Y.Y.YYY" received signal SIGSEGV, Segmentation fault. ---Type
to continue, or q to quit---
Switch to this terminal, maximise it and press “return” (Enter). Then type
Select the entire backtrace. Now open a text editor and middle click within the text area. This will “paste” the contents of your Primary Buffer. Send it along to us as a reply to the email we sent you after logging your bug report.
You can now quit the browser as normal.