Research crashes

ldexterldesign

Hi all,

Hope you're well

Thanks for software

I've been experiencing Vivaldi crashes recently (i.e. past few weeks); in what's usually a very stable browser

What's the process for diagnosing the issue?

macOS generates a "report" but unsure if this is helpful in diagnosis

If you have any issues (e.g. questions/queries) happy to help

Hope to hear back

Keep up great work!

Yours faithfully

xyzzy

@ldexterldesign There's not much that you can do to diagnose the crash but it's very helpful if you can reproduce the crash consistently, open Console.app and locate the crash log in the User Diagnostic Reports section, submit a bug report, and then respond to the confirmation e-mail and attach a copy of the crash log.

As an internal tester, I do the same but I also try to go the extra steps of reproducing the crash with a new/clean/default Vivaldi installation. If it looks like a bug in the Chromium code, I'll also try to reproduce the bug with Google Chrome.

If you can't get the crash to reproduce consistently, please post to the Forums, let us know what you were doing when the crash occurred and, if applicable, the site where the crash triggers, and we'll do our best to help you out. If you also post the trace for the crashed thread and the version of Vivaldi that you are using, we should also be able to confirm whether or not this is a known issue.

Thanks!

ldexterldesign

Thanks for reply

Noted

Aside, it would be super useful if what you just explained was wrapped in some UX post crash for end users

Cheers

xyzzy

@ldexterldesign Thanks, I'll pass that request along. https://help.vivaldi.com also has an article for Windows users on how to report a crash and submit a crash report. At the very least, we should provide the same guidance for Mac and Linux users as well.

Do you have any details that you can share about your crash? Are you able to replicate it to any degree or does it seem to occur randomly? Are you using Snapshot builds or the latest Stable release?

Thanks again!

ldexterldesign

I was able to reproduce it and was sure it was a specific extension but I have since experienced crashes with said extension disabled. Besides the suspected extension, my use case (i.e. reproduced consistently) was running find in page on a youtube video where I had maxed out the comments infinite scroll; the page had hundreds of comments.

Also my free disk space has been low (e.g. <10/250GB) for a while which can't help

I will report back here next time it happens with more info'

Cheers

ldexterldesign

Report log: https://drive.google.com/open?id=1zBO2pdxLz7ptd3p7JDIQiTgDd_n4xP5j

Hope this helps and to hear back!

Regards

PS I did scan through but if there's any sensitive info' in that log file please let me know so I can remove it after you've finished

ldexterldesign

FYI

https://chrome.google.com/webstore/detail/reading-time/nccohhimobidpghgpnejnbkpoichbbml - this extension is the crash cause, notably when I use "Find in page"

Hope this is useful

Regards

xyzzy

@ldexterldesign Thanks for identifying the what was triggering your crash. Could you please file a bug report for this? When you get the bug confirmation email, please also reply to it and attach the crash log. I'll then try to confirm it and the devs can then start working on a fix.

Thanks again!

ldexterldesign

Created bug report and included a URL to this forum thread (logs + context), where access to the log files will stay live

When you get the bug confirmation email, please also reply to it and attach the crash log

If I still need to reply to the email with the logs ping this thread and I'll action that

Good luck!

Cheers

ldexterldesign

FYI
NO REPLY NECESSARY

I just had a crash using "Find in page" without the extension installed which suggests the crash could be a Vivaldi core issue after all

If I can reproduce I'll follow up here

NB I've added a new log[g]

Regards

[g] https://drive.google.com/open?id=1zBO2pdxLz7ptd3p7JDIQiTgDd_n4xP5j

AltCode

I've had a few find in page crashes myself as of lately, so I'll share my experience so far. First of all, it has only happened to me in a few select websites:

Wikipedia
The Vivaldi blog
Twitter
YouTube
NintendoLife

The only extension that is ever running is an adblocker, with the exception being the Vivaldi blog, where no extensions run at all. As you can probably guess, a lot of text is generally displayed on these websites.

The crash only ever happens when I try to change the keyword that I am trying to "find in page", by selecting it all and then trying to delete it.

Here is the last crash log that I received: https://drive.google.com/open?id=1jo9rjMsHbSi60sXKoywsUoY4as1NR8iX

EDIT
Here is another crash report that I just got today: https://drive.google.com/open?id=1-_mQK9pt71eNTLfKmdqkC8I_2EY233-9

ldexterldesign

@gwen-dragon yes, https://forum.vivaldi.net/post/254656

ldexterldesign

Curious to know if this issue was diagnosed/fixed - assuming blog snapshots[s] is the correct place to look I can't find anything relevant?

Hope to hear back

Cheers

[s] https://vivaldi.com/blog/snapshots/

ldexterldesign

This post is deleted!

ldexterldesign

@Gwen-Dragon [Jira] (VB-46506) Review extension (reading time) causing browser crash

Cheers

ldexterldesign

@Gwen-Dragon great, no issues since; just curious. Thanks.

ldexterldesign

The find in page bug is back and it's crashing my browser

I've added a new log[l] but let me know if you'd prefer a new bug report

Switching to another browser until this is fixed

Regards

l: https://drive.google.com/open?id=1zBO2pdxLz7ptd3p7JDIQiTgDd_n4xP5j

rseiler

It's unclear to me if crashes and freezes are related. I added what I'm seeing in v2.3 (and just that version) to the second thread that you linked to above.

ldexterldesign

Ahh, unless I'm mistaken the "find in page" issue is a regression[r] Vivaldi is aware of:

[Regression] Vivaldi hangs by find-in-page under certain conditions (VB-49066)

Regards

r: https://vivaldi.com/blog/minor-update-for-vivaldi-2-3/

rseiler

@ldexterldesign That was about the hang version of the problem. There's a full-blown crash version of the problem also going around.