Submiting crash dumps
-
@ruario @Ayespy @Gwen-Dragon
I think that Vivaldi should provide separate upload form for registered users to upload memory dumps.
Sometimes opening a new ticket is just hard because all I got to describe is "Vivaldi crashed unexpectedly" and I can't provide any steps to reproduce problem...More to say - I think that 99% of users don't have WinDbg so they won't be able to even provide details like bugcheck codes etc.
Also I have no idea if Vivaldi team want to analyze memory dumps taken in previous Snapshot veriosns...
-
@gwen-dragon I saw it.
I don't know if Sopranos like to deal with tickets described like "Vivaldi crashed and I have no idea how to reproduce it" (because it's how latest Snapshots behave ).
Also I doubt that Sopranos have access to symbols to extract stack trace...So I guess without details these tickets could be closed as "cannot reproduce" as well...
-
I just have doubts how to properly submit dumps...
Should I create separate issue for each crash?
Or group crashes by Snapshot version?...
Or group crashes by something else? -
@gwen-dragon It just happens while I use Vivaldi as usual. Usually after some hours/days.
Dunno... maybe it's about some of my usage schemes like using many tabs or I don't know...Thanks!
-
@rotfl If you are of the opinion that the crashes are caused by the same or a similar reason it should suffice to send the latest crashlog as reply to the confirmation mail you've got from the bugtracker.
Crashes of old snapshots are less helpful because it would mean that someone has to analyze stuff that already might be fixed by later snapshots.
It would be of course better if you could somehow manage to make the crash reproducible for people who don't use the same profile as you, so please try to remember the last things you did short before it crashed, e.g. clicked on this button, scrolled a bit, watched this (full url) video, etc. pp.
Hint: The crashlogs compress really well. Zip them before attaching to the reply mail - makes uploads much smaller.
-
@rotfl said in Submiting crash dumps:
Should I create separate issue for each crash?
Or group crashes by Snapshot version?...
Or group crashes by something else?Separate issue for each crash. If they turn out to be the same, we would dupe them internally
If it turns out that everything you are submitting is the same crash we might ping you and tell you so. To avoid you having to keep logging new issues.
-
@quhno The problem is.... it's hard to say what the cause is
I guess that's probably ordinary access violation (AV) / segmentation fault (segfault) caused by dangling pointer or memory leak...@ruario Thanks, that's a really valuable information.
You should include it on https://help.vivaldi.com/article/reporting-crashes-on-windows/Which Snapshots are treated as "old"? 1.15.x? Or all except the latest one?
-
Old is anything older than the latest stable / snapshot available. It's always better to get the crash with the latest Stable or Snapshot as it's the closest to the current master branch the team is working on.
-
-