Weird crashes since upgrading to Vivaldi 2.3
-
@ruario Thank you for the instructions. I installed the x64 binary and I am running it now under gdb. Will post results once I experience the next crash.
-
@Gwen-Dragon said in Weird crashes since upgrading to Vivaldi 2.3:
Please read how to Report a bug for Vivaldi carefully and then report the bug to Vivaldi bugtracker.
Just FYI, I did this several weeks ago without ever receiving an answer. I would have happily supplied them with debug data, but I never received a reply to my bug report. That's why I started posting on this forum in the first place!
-
@Gwen-Dragon
there you go:Summary: Frequent crashes upon upgrading to 2.3 Key: VB-50555 Project: Vivaldi Browser Environment: Vivaldi version: 2.3.1440.60
-
@ruario I'll give it a shot. Since I can't reproduce consistently, it might take a while to get results.
-
@Gwen-Dragon said in Weird crashes since upgrading to Vivaldi 2.3:
@ferdiG Sorry, but you should update to Vivaldi 2.4.
And next time if you have crashlogs send them as a attached textfile in a mail reply.FYI I have been running 2.4 for several weeks now. It's just that the crashes did not go away since upgrading from 2.3 to 2.4 ...
Anyway, we can cut this "discussion" short. I will just submit another bug report once I get a backtrace out of the binary that @ruario kindly supplied. Have a nice day.
-
We just released a minor update, so here are some updated debug binaries
- Download a suitable Vivaldi binary (with debugging symbols)
-
@ruario
I just submitted a new bug report for vivaldi-2.4.1488.36-x64-debug containing a backtrace:
Your bug report has been given the issue reference VB-52068The binary vivaldi-2.4.1488.38-x64-debug crashes immediately on my system with a SIGTRAP both under gdb and without. It's final words are:
# # Fatal error in , line 0 # Version mismatch between V8 binary and snapshot. # V8 binary version: 7.3.492.27 # Snapshot version: 7.3.492.25 # The snapshot consists of 287384 bytes and contains 1 context(s). # # # #FailureMessage Object: 0x7ffc6bb0e3c0#0 0x5648b077b4f9 <unknown>
If you want, I can provide a backtrace for .38 as well.
-
@ferdiG said in Weird crashes since upgrading to Vivaldi 2.3:
The binary vivaldi-2.4.1488.38-x64-debug crashes immediately
never mind, just did a pacman -Syu, running it under gdb now ...
-
@ruario I was finally able to get a backtrace as well. I reported it as: VB-52104
[New Thread 0x7fffc364b700 (LWP 7748)] [New Thread 0x7fffdd87f700 (LWP 7751)] [New Thread 0x7fffacbeb700 (LWP 7891)] [New Thread 0x7fff9fa69700 (LWP 8045)] [New Thread 0x7fff9f268700 (LWP 8046)] [New Thread 0x7fff9cee4700 (LWP 8061)] [New Thread 0x7fff9c263700 (LWP 8062)] [New Thread 0x7fff9ba62700 (LWP 8063)] [New Thread 0x7fff9b261700 (LWP 8064)] [New Thread 0x7fff9aa60700 (LWP 8065)] [New Thread 0x7fff97b5b700 (LWP 8096)] [Thread 0x7fffdd87f700 (LWP 7751) exited] [Thread 0x7fffa12ea700 (LWP 7747) exited] [Thread 0x7fffc8258700 (LWP 6170) exited] [1:14:0414/140516.805252:ERROR:render_media_log.cc(30)] MediaEvent: MEDIA_ERROR_LOG_ENTRY {"error":"video decoder initialization failed"} [1:1:0414/140516.808024:ERROR:render_media_log.cc(30)] MediaEvent: PIPELINE_ERROR DECODER_ERROR_NOT_SUPPORTED [1:14:0414/140532.284306:ERROR:render_media_log.cc(30)] MediaEvent: MEDIA_ERROR_LOG_ENTRY {"error":"video decoder initialization failed"} [1:1:0414/140532.337076:ERROR:render_media_log.cc(30)] MediaEvent: PIPELINE_ERROR DECODER_ERROR_NOT_SUPPORTED [New Thread 0x7fffc8258700 (LWP 8946)] [Thread 0x7fffe5929700 (LWP 7179) exited] [New Thread 0x7fffe5929700 (LWP 8996)] Thread 1 "vivaldi-2.4.148" received signal SIGSEGV, Segmentation fault. 0x0000555557f817d2 in SendMouseEnterOrLeaveEvents () at ./../../chromium/content/browser/renderer_host/render_widget_host_input_event_router.cc:888 888 ./../../chromium/content/browser/renderer_host/render_widget_host_input_event_router.cc: No such file or directory. (gdb) bt #0 0x0000555557f817d2 in SendMouseEnterOrLeaveEvents () at ./../../chromium/content/browser/renderer_host/render_widget_host_input_event_router.cc:888 #1 0x0000555557f817d2 in DispatchMouseEvent () at ./../../chromium/content/browser/renderer_host/render_widget_host_input_event_router.cc:576 #2 0x0000555557f817d2 in DispatchEventToTarget() () at ./../../chromium/content/browser/renderer_host/render_widget_host_input_event_router.cc:1722 #3 0x0000555557f941c4 in FoundTarget() () at ./../../chromium/content/browser/renderer_host/render_widget_targeter.cc:483 #4 0x0000555557f95a4b in FoundFrameSinkId() () at ./../../chromium/content/browser/renderer_host/render_widget_targeter.cc:418 #5 0x0000555557faf3de in Invoke<void (content::RenderWidgetTargeter::*)(base::WeakPtr<content::RenderWidgetHostViewBase>, base::WeakPtr<content::RenderWidgetHostViewBase>, std::__1::unique_ptr<blink::WebInputEvent, ui::WebInputEventDeleter>, ui::LatencyInfo const&, unsigned int, gfx::PointF const&, content::TracingUmaTracker, viz::FrameSinkId const&, viz::FrameSinkId const&, gfx::PointF const&), base::WeakPtr<content::RenderWidgetTargeter>, base::WeakPtr<content::RenderWidgetHostViewBase>, base::WeakPtr<content::RenderWidgetHostViewBase>, std::__1::unique_ptr<blink::WebInputEvent, ui::WebInputEventDeleter>, ui::LatencyInfo, unsigne---Type <return> to continue, or q <return> to quit---
-
I just submitted another bug report, too: VB-52130. It does not contain a backtrace however since it was one of those "other" crashes, where the browser just would not update its window contents anymore. Had to kill it off, did supply strace output... maybe it is of any help. Before freezing the browser wrote several of these messages to the console:
[12969:12969:0415/142437.148315:ERROR:gles2_cmd_decoder.cc(10403)] [.DisplayCompositor]RENDER WARNING: texture bound to texture unit 0 is not renderable. It maybe non-power-of-2 and have incompatible texture filtering.
-
Hi guys,
I've been getting this problem for a while now too, definitely on 2.3 and now definitely on 2.4. I get 2-3 times a day, just long pauses for 10+ seconds, no repaint, CPU usage starts going up. Plenty of cores and RAM available so it shouldn't be struggling. Also running Arch Linux.
How can I best help?
-
I have the same issue on Arch Linux with 2.4.1488.38 build. Vivaldi crashes every day for several months. If problem not be solved with the other members help I'll install debug version and try to catch crash.
-
Is there any news?
-
-
@BiTOk Other than the log that I provided above and in VB-52104, I don't have anymore logs to provide.
Actually, I don't think I've had a crash in a while.
-
@Gwen-Dragon Where can I get debug build for 2.5.1525.40? It crashed yesterday again.
-
I've catched the crash and sent report VB-53418. Now waiting for fix.
-
@Gwen-Dragon what about VB-53418?
-
In order not to create a new thread (since I also saw unstable behavior described here) - does anybody experience periodical crashes by F5ing a page (no matter if it is a key or mouse)?
Probably it happens more often with the debug console enabled (but it is also possible that I am reloading pages more often with this tool enabled). -
@Gwen-Dragon any news about VB-53418?