Crash log & report submission (under Linux)
I'm running Vivaldi 1.15.1147.36 (Stable channel) (64-bit) on Linux Mint 17.3 (based on Ubuntu 14.04)
I have seen several times that Vivaldi crashes when I press F12 in order to open the debug panel. However, I am not able to find any related log file for this.
Marko Indaco last edited by Marko Indaco
Hi @feng32 , F12 works fine for me. I'm with Mint 18.2 (Cinnamon - 64bit). Try to Exit Vivaldi, open Terminal and type:
Wait for Vivaldi boot, then press F12 and look at the Terminal window for eventually new messages.
Hi @Marko-Indaco Vivaldi crashes sometimes on my Linux Mint 17.3 64bit (MATE Desktop).
I started vivaldi with "-sustart" option in console yesterday, and now It crashes due to segmentation fault. Here's the stderr log:
(the full log is classified as spam, so I will describe what it looks like manually)
- a lot of:
[10244:10244:0529/163043.186793:ERROR:gl_surface_presentation_helper.cc(104)] GetVSyncParametersIfAvailable() failed!
- a few:
[10152:10152:0529/163540.943319:ERROR:CONSOLE(1)] "Uncaught (in promise) SyntaxError: Unexpected identifier", source: chrome-devtools://devtools/bundled/inspector.html?remoteBase=https://chrome-devtools-frontend.appspot.com/serve_file/@166efd59c7aba158f456fc82eabf5d0dffdc41f5/&can_dock=true&dockSide=undocked (1)
- a few:
[10152:10192:0529/163604.475258:ERROR:socket_dispatcher_host.cc(91)] Failed to resolve address for x., errorcode: -137
- the last line:
feng32 last edited by feng32
@Marko-Indaco This screenshot is not very helpful. However, the vivaldi crash on my system is rather easy to capture (chromium never crashes). If the development team needs any further information, I am ready to help
Marko Indaco last edited by Pesala
@feng32 hi, I guess your first post and the screenshot should be enough to understand what's going on. Unfortunately, I haven't the skills to understand what goes wrong, sorry. I tried a little Google search, but I could not find anything that seems related... Anyone?
Segmentation fault is an critical error that appears in programs written in C/C++ (under Linux) due to incorrect use of pointers. Under Linux we can enable core dump and then collect the dumped file for later analysis with gdb, which requires the debug version of the executable.
I can write C/C++ programs for Linux servers / desktops, but I don't know much about the back-end technology of Vivaldi.