I have been unable to reproduce this issue. There may be some specific settings, properties of the crash, or hidden state involved. In my attempt to reproduce the issue, I've been using `about:crashcontent` to create new crashes and closing the crashed tab without submitting a crash report. After this, `about:crashes` always shows an unsubmitted crash. I then close the browser and re-open it. I temporarily modified the unsubmitted crash report timer to be 10 seconds instead of 10 minutes. After that goes off, the notification is shown. I tried both a normal "Submit" and "Always", both cases worked as expected with `about:crashes` immediately showing the crash as submitted. I also tried this again after "Always" (e.g. with "Allow Nightly to send backlogged crash reports on your behalf" set) as I mentioned in [above](https://bugzilla.mozilla.org/show_bug.cgi?id=1322097#c2). With this set, shortly after starting up firefox again `about:crashes` shows the crash as being sent (and the notification did not come up). When reading the code, however, I saw that the crash reports that are submitted are limited to the past 28 days. Unfortunately my previous comment was long enough ago that I cannot check whether that particular crash occurred prior to the 28 day limit. Though it's worth noting that I only see one crash reported in my `about:crashes` on that date, so if a more recent crash had triggered the notification _and_ there was an older crash, I would have expected to see two crashes submitted on that date (one automatically, one manually). The fact that the notification came up when I thought I had "Allow Nightly to send backlogged crash reports on your behalf" is an indication of something very messed up, since that should immediately stop the notification from being shown as far as I can tell. But maybe I was mistaken, or the profile had been wiped. :nika, do you remember the details of the behavior you saw?
Bug 1322097 Comment 4 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
I have been unable to reproduce this issue. There may be some specific settings, properties of the crash, or hidden state involved. In my attempt to reproduce the issue, I've been using `about:crashcontent` to create new crashes and closing the crashed tab without submitting a crash report. After this, `about:crashes` always shows an unsubmitted crash. I then close the browser and re-open it. I temporarily modified the unsubmitted crash report timer to be 10 seconds instead of 10 minutes. After that goes off, the notification is shown. I tried both a normal "Submit" and "Always", both cases worked as expected with `about:crashes` immediately showing the crash as submitted. I also tried this again after "Always" (e.g. with "Allow Nightly to send backlogged crash reports on your behalf" set) as I mentioned [above](https://bugzilla.mozilla.org/show_bug.cgi?id=1322097#c2). With this set, shortly after starting up firefox again `about:crashes` shows the crash as being sent (and the notification did not come up). When reading the code, however, I saw that the crash reports that are submitted are limited to the past 28 days. Unfortunately my previous comment was long enough ago that I cannot check whether that particular crash occurred prior to the 28 day limit. Though it's worth noting that I only see one crash reported in my `about:crashes` on that date, so if a more recent crash had triggered the notification _and_ there was an older crash, I would have expected to see two crashes submitted on that date (one automatically, one manually). The fact that the notification came up when I thought I had "Allow Nightly to send backlogged crash reports on your behalf" is an indication of something very messed up, since that should immediately stop the notification from being shown as far as I can tell. But maybe I was mistaken, or the profile had been wiped. :nika, do you remember the details of the behavior you saw?
I have been unable to reproduce this issue. There may be some specific settings, properties of the crash, or hidden state involved. In my attempt to reproduce the issue, I've been using `about:crashcontent` to create new crashes and closing the crashed tab without submitting a crash report. After this, `about:crashes` always shows an unsubmitted crash. I then close the browser and re-open it. I temporarily modified the unsubmitted crash report timer to be 10 seconds instead of 10 minutes. After that goes off, the notification is shown. I tried both a normal "Submit" and "Always", both cases worked as expected with `about:crashes` immediately showing the crash as submitted. I also tried this again after "Always" (e.g. with "Allow Nightly to send backlogged crash reports on your behalf" set) as I mentioned [above](https://bugzilla.mozilla.org/show_bug.cgi?id=1322097#c2). With this set, shortly after starting up firefox again `about:crashes` shows the crash as being sent (and the notification did not come up). When reading the code, however, I saw that the crash reports that are submitted are limited to the past 28 days. Unfortunately my previous comment was long enough ago that I cannot check whether that particular crash occurred prior to the 28 day limit. Though it's worth noting that I only see one crash reported in my `about:crashes` on that date, so if a more recent crash had triggered the notification _and_ there was an older crash, I would have expected to see two crashes submitted on that date (one from the notification, one manually). The fact that the notification came up when I thought I had "Allow Nightly to send backlogged crash reports on your behalf" is an indication of something very messed up, since that should immediately stop the notification from being shown as far as I can tell. But maybe I was mistaken, or the profile had been wiped. :nika, do you remember the details of the behavior you saw?
I have been unable to reproduce this issue. There may be some specific settings, properties of the crash, or hidden state involved. In my attempt to reproduce the issue, I've been using `about:crashcontent` to create new crashes and closing the crashed tab without submitting a crash report. After this, `about:crashes` always shows an unsubmitted crash. I then close the browser and re-open it. I temporarily modified the unsubmitted crash report timer to be 10 seconds instead of 10 minutes. After that goes off, the notification is shown. I tried both a normal "Submit" and "Always", both cases worked as expected with `about:crashes` immediately showing the crash as submitted. I also tried this again after "Always" (e.g. with "Allow Nightly to send backlogged crash reports on your behalf" set) as I mentioned [above](https://bugzilla.mozilla.org/show_bug.cgi?id=1322097#c2). With this set, shortly after starting up firefox again `about:crashes` shows the crash as being sent (and the notification did not come up). When reading the code, however, I saw that the crash reports that are submitted are limited to the past 28 days. Unfortunately my previous comment was long enough ago that I cannot check whether that particular crash occurred prior to the 28 day limit. Though it's worth noting that I only see one crash reported in my `about:crashes` on that date, so if a more recent crash had triggered the notification _and_ there was an older crash, I would have expected to see two crashes submitted on that date (one from the notification, one manually). The fact that the notification came up when I thought I had "Allow Nightly to send backlogged crash reports on your behalf" is an indication of something very messed up, since that should immediately stop the notification from being shown as far as I can tell. But maybe I was mistaken, or the profile had been wiped. As a final note, it's possible that _something_ prevented the crash report from being submitted (something failed). In this case, we don't have any avenue of providing UI feedback to the user, so that would result in a crash remaining unsubmitted. Though the unsubmitted check happens every 10 minutes, and in my previous comment I mentioned that I waited hours and didn't see it submitted (nor any new notifications). :nika, do you remember the details of the behavior you saw?