[Desktop-packages] [Bug 1917191]
Ugh, this bug is affecting Linux users real badly on 86. Do we have a way to reach out to distro maintainers to try and help them roll out a local fix for their 86 builds? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1917191 Title: firefox will not start after it crashed unexpectedly Status in Mozilla Firefox: Fix Released Status in firefox package in Ubuntu: Confirmed Bug description: firefox crashed unexpectedly, and it will not start or restart. I am running the latest ubuntu-20.04.2 LTS, all updates applied. firefox 86.0+build3 --- ProblemType: Bug AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: johnfg 1725 F pulseaudio /dev/snd/controlC1: johnfg 1725 F pulseaudio BuildID: 20210222142601 CasperMD5CheckResult: skip Channel: Unavailable CurrentDesktop: ubuntu:GNOME DefaultProfileExtensions: extensions.sqlite corrupt or missing DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) DefaultProfileLocales: extensions.sqlite corrupt or missing DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:348 DefaultProfilePrefSources: prefs.js DefaultProfileThemes: extensions.sqlite corrupt or missing DistroRelease: Ubuntu 20.04 ForcedLayersAccel: False InstallationDate: Installed on 2020-02-22 (371 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) IpRoute: default via 192.168.1.1 dev wlp10s0 proto dhcp metric 600 10.8.0.0/24 via 10.8.0.17 dev tun0 10.8.0.17 dev tun0 proto kernel scope link src 10.8.0.18 169.254.0.0/16 dev wlp10s0 scope link metric 1000 192.168.1.0/24 dev wlp10s0 proto kernel scope link src 192.168.1.8 metric 600 NonfreeKernelModules: openafs Package: firefox 86.0+build3-0ubuntu0.20.04.1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.4.0-66.74-generic 5.4.86 Profile0Extensions: extensions.sqlite corrupt or missing Profile0IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile0Locales: extensions.sqlite corrupt or missing Profile0PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:348 Profile0PrefSources: prefs.js Profile0Themes: extensions.sqlite corrupt or missing Profiles: Profile1 (Default) - LastVersion=80.0/20200818235255 (Out of date) Profile0 - LastVersion=86.0/20210222142601 RunningIncompatibleAddons: False Tags: focal Uname: Linux 5.4.0-66-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-04-24 (309 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/05/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V4.00L12 dmi.board.asset.tag: No Asset Tag dmi.board.name: CF52-4 dmi.board.vendor: Panasonic Corporation dmi.board.version: 1 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Panasonic Corporation dmi.chassis.version: 001 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV4.00L12:bd07/05/2011:svnPanasonicCorporation:pnCF-52SLGDD1M:pvr004:rvnPanasonicCorporation:rnCF52-4:rvr1:cvnPanasonicCorporation:ct10:cvr001: dmi.product.family: CF52-4 dmi.product.name: CF-52SLGDD1M dmi.product.sku: CF-52SLGDD1M dmi.product.version: 004 dmi.sys.vendor: Panasonic Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1917191/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1849615]
(In reply to Ryan VanderMeulen [:RyanVM] from comment #13) > Looks like this grafts cleanly to ESR68 - did you want to nominate it for > uplift? Yes, let's do it. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1849615 Title: WebRTC-related crashes Status in Mozilla Firefox: Fix Released Status in firefox package in Ubuntu: Fix Committed Bug description: In Mozilla we've detected a spike of crashes in the Ubuntu-packaged version of Firefox 69.0.x. All the crashes are happening in the WebRTC code and specifically libc's FD_SET, FD_CLR and FD_ISSET range- checking safety is causing an abort. Is it possible that Firefox is being built with a FD_SETSIZE value that's different from what's used in libc? To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1849615/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1849615]
Comment on attachment 9104623
Bug 1590984 - Use poll() instead of select() in WebRTC code r=drno
### ESR Uplift Approval Request
* **If this is not a sec:{high,crit} bug, please state case for ESR
consideration**: This fixes a crash that can easily occur when using WebRTC.
* **User impact if declined**: Firefox may crash when using WebRTC; this will
happen independently of the user since it's triggered by the file descriptor
numbers used by the WebRTC devices (camera, microphone, etc...).
* **Fix Landed on Version**: 72
* **Risk to taking this patch**: Low
* **Why is the change risky/not risky? (and alternatives if risky)**: The fix
is small and almost mechanical and the patch has been in nightly and then beta
for two months now without causing regressions.
* **String or UUID changes made by this patch**: None
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/1849615
Title:
WebRTC-related crashes
Status in Mozilla Firefox:
Fix Released
Status in firefox package in Ubuntu:
Fix Committed
Bug description:
In Mozilla we've detected a spike of crashes in the Ubuntu-packaged
version of Firefox 69.0.x. All the crashes are happening in the WebRTC
code and specifically libc's FD_SET, FD_CLR and FD_ISSET range-
checking safety is causing an abort. Is it possible that Firefox is
being built with a FD_SETSIZE value that's different from what's used
in libc?
To manage notifications about this bug go to:
https://bugs.launchpad.net/firefox/+bug/1849615/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1849615]
There's quite a few crashes coming from ESR68 on Debian. The patch is not large and low-risk, maybe we could uplift it. I'll see if it applies cleanly there. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1849615 Title: WebRTC-related crashes Status in Mozilla Firefox: Fix Released Status in firefox package in Ubuntu: Fix Committed Bug description: In Mozilla we've detected a spike of crashes in the Ubuntu-packaged version of Firefox 69.0.x. All the crashes are happening in the WebRTC code and specifically libc's FD_SET, FD_CLR and FD_ISSET range- checking safety is causing an abort. Is it possible that Firefox is being built with a FD_SETSIZE value that's different from what's used in libc? To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1849615/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1849615]
No testing is needed, thanks Catalin. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1849615 Title: WebRTC-related crashes Status in Mozilla Firefox: Fix Released Status in firefox package in Ubuntu: Fix Committed Bug description: In Mozilla we've detected a spike of crashes in the Ubuntu-packaged version of Firefox 69.0.x. All the crashes are happening in the WebRTC code and specifically libc's FD_SET, FD_CLR and FD_ISSET range- checking safety is causing an abort. Is it possible that Firefox is being built with a FD_SETSIZE value that's different from what's used in libc? To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1849615/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1849615]
Taking this as I've got a WIP patch. It just needs some good testing. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1849615 Title: WebRTC-related crashes Status in Mozilla Firefox: Fix Released Status in firefox package in Ubuntu: New Bug description: In Mozilla we've detected a spike of crashes in the Ubuntu-packaged version of Firefox 69.0.x. All the crashes are happening in the WebRTC code and specifically libc's FD_SET, FD_CLR and FD_ISSET range- checking safety is causing an abort. Is it possible that Firefox is being built with a FD_SETSIZE value that's different from what's used in libc? To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1849615/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1849615]
Created attachment 9104623 Bug 1590984 - Use poll() instead of select() in WebRTC code r=drno The use of select() was leading to crashes when the file descriptor value was larger than FD_SETSIZE. Recent versions of glibc have checks in the FD_CLR(), FD_SET() and FD_ISSET() macros that will abort() the program instead of doing an out-of-bounds access. poll() doesn't have limitations on the file descriptor values and provides behavior that is otherwise identical to select() thus solving the problem. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1849615 Title: WebRTC-related crashes Status in Mozilla Firefox: Fix Released Status in firefox package in Ubuntu: New Bug description: In Mozilla we've detected a spike of crashes in the Ubuntu-packaged version of Firefox 69.0.x. All the crashes are happening in the WebRTC code and specifically libc's FD_SET, FD_CLR and FD_ISSET range- checking safety is causing an abort. Is it possible that Firefox is being built with a FD_SETSIZE value that's different from what's used in libc? To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1849615/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1849615]
(In reply to Dan Minor [:dminor] from comment #3) > Hi Gabriele, this code is our local modification to webrtc.org that we have > never merged upstream. As such, feel free to rewrite it to use poll() if that > will fix things. I'm not the original author, I just happened to do the last > upstream merge, so I can't comment on why select was chosen rather than poll. > :jesup might know if you want to follow up with him. > > One thing to be careful of is that this code is handling cameras being > plugged and unplugged which is not something we have coverage for in > automation, so you'll have to do some manual testing of your changes. The STR > from https://bugzilla.mozilla.org/show_bug.cgi?id=1581193#c0 might be helpful > here. Thanks, I'll try to cook up a patch tomorrow. I must have a USB camera sitting around somewhere so testing shouldn't be a problem. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1849615 Title: WebRTC-related crashes Status in Mozilla Firefox: Confirmed Status in firefox package in Ubuntu: New Bug description: In Mozilla we've detected a spike of crashes in the Ubuntu-packaged version of Firefox 69.0.x. All the crashes are happening in the WebRTC code and specifically libc's FD_SET, FD_CLR and FD_ISSET range- checking safety is causing an abort. Is it possible that Firefox is being built with a FD_SETSIZE value that's different from what's used in libc? To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1849615/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1849615] Re: WebRTC-related crashes
Nevermind, this isn't WebRTC-specific and not even Ubuntu-specific since I could find Debian instances of it. It's caused by select() being used instead of more modern methods that don't have limits on the file descriptor values you pass to them. Sorry for the noise. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1849615 Title: WebRTC-related crashes Status in Mozilla Firefox: Unknown Status in firefox package in Ubuntu: New Bug description: In Mozilla we've detected a spike of crashes in the Ubuntu-packaged version of Firefox 69.0.x. All the crashes are happening in the WebRTC code and specifically libc's FD_SET, FD_CLR and FD_ISSET range- checking safety is causing an abort. Is it possible that Firefox is being built with a FD_SETSIZE value that's different from what's used in libc? To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1849615/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1849615] Re: WebRTC-related crashes
I did some further digging and this isn't a WebRTC-specific issue though it tends to crash WebRTC code more often than other code. See this for another similar crash in code we don't control (and which might also be using select() and thus triggering the safety check): https://crash-stats.mozilla.com/report/index/d347998e-6c60-4761-aece- e7e8c0191023 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1849615 Title: WebRTC-related crashes Status in firefox package in Ubuntu: New Bug description: In Mozilla we've detected a spike of crashes in the Ubuntu-packaged version of Firefox 69.0.x. All the crashes are happening in the WebRTC code and specifically libc's FD_SET, FD_CLR and FD_ISSET range- checking safety is causing an abort. Is it possible that Firefox is being built with a FD_SETSIZE value that's different from what's used in libc? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1849615/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1849615] [NEW] WebRTC-related crashes
Public bug reported: In Mozilla we've detected a spike of crashes in the Ubuntu-packaged version of Firefox 69.0.x. All the crashes are happening in the WebRTC code and specifically libc's FD_SET, FD_CLR and FD_ISSET range-checking safety is causing an abort. Is it possible that Firefox is being built with a FD_SETSIZE value that's different from what's used in libc? ** Affects: firefox (Ubuntu) Importance: Undecided Status: New ** Bug watch added: Mozilla Bugzilla #1590984 https://bugzilla.mozilla.org/show_bug.cgi?id=1590984 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1849615 Title: WebRTC-related crashes Status in firefox package in Ubuntu: New Bug description: In Mozilla we've detected a spike of crashes in the Ubuntu-packaged version of Firefox 69.0.x. All the crashes are happening in the WebRTC code and specifically libc's FD_SET, FD_CLR and FD_ISSET range- checking safety is causing an abort. Is it possible that Firefox is being built with a FD_SETSIZE value that's different from what's used in libc? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1849615/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1849615] Re: WebRTC-related crashes
Here's the relevant bug on our tracker: https://bugzilla.mozilla.org/show_bug.cgi?id=1590984 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1849615 Title: WebRTC-related crashes Status in firefox package in Ubuntu: New Bug description: In Mozilla we've detected a spike of crashes in the Ubuntu-packaged version of Firefox 69.0.x. All the crashes are happening in the WebRTC code and specifically libc's FD_SET, FD_CLR and FD_ISSET range- checking safety is causing an abort. Is it possible that Firefox is being built with a FD_SETSIZE value that's different from what's used in libc? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1849615/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1845205] Re: Cannot submit crash reports from firefox' "this tab crashed" page
Interesting, that shouldn't happen. The minidump-analyzer executable greatly improves our crash telemetry but it's not strictly needed for crash reporting. I'll file a bug on our side to fix that issue. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1845205 Title: Cannot submit crash reports from firefox' "this tab crashed" page Status in firefox package in Ubuntu: In Progress Bug description: Steps to reproduce: - Launch firefox - Enter "about:crashcontent" in the URL bar - Upon hitting return, the tab should crash and display the "This tab just crashed" page - Ensure that the checkmark to send the crash report is ticked - Add a comment (anything will do, a non-empty comment ensures that the crash is accepted by Mozilla crash reporting back-end) - Click on "Restore this tab" - Go to the "about:crashes" page Expected behaviour: In the "about:crashes" page the crash is displayed among the submitted crash reports, showing that the crash report was indeed submitted correctly. Actual behaviour: The crash appears among the unsubmitted crashes. This bug is specific to the packaged version of Firefox that comes with Ubuntu. I've tried reproducing using Mozilla's builds and crash submission works correctly there. See this bug https://bugzilla.mozilla.org/show_bug.cgi?id=1583247 on Mozilla's tracker regarding this behaviour. In Mozilla we noticed the issue because we've started properly processing crash reports coming from Ubuntu and tab crashes were strangely few. Feel free to contact me directly at gsve...@mozilla.com about this issue since I'm in charge of Firefox crash reporting machinery. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1845205/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1845205] Re: Cannot submit crash reports from firefox' "this tab crashed" page
Yes, manual submission via about:crashes works fine. It's just the tab crash reporter that doesn't show up as it should. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1845205 Title: Cannot submit crash reports from firefox' "this tab crashed" page Status in firefox package in Ubuntu: Confirmed Bug description: Steps to reproduce: - Launch firefox - Enter "about:crashcontent" in the URL bar - Upon hitting return, the tab should crash and display the "This tab just crashed" page - Ensure that the checkmark to send the crash report is ticked - Add a comment (anything will do, a non-empty comment ensures that the crash is accepted by Mozilla crash reporting back-end) - Click on "Restore this tab" - Go to the "about:crashes" page Expected behaviour: In the "about:crashes" page the crash is displayed among the submitted crash reports, showing that the crash report was indeed submitted correctly. Actual behaviour: The crash appears among the unsubmitted crashes. This bug is specific to the packaged version of Firefox that comes with Ubuntu. I've tried reproducing using Mozilla's builds and crash submission works correctly there. See this bug https://bugzilla.mozilla.org/show_bug.cgi?id=1583247 on Mozilla's tracker regarding this behaviour. In Mozilla we noticed the issue because we've started properly processing crash reports coming from Ubuntu and tab crashes were strangely few. Feel free to contact me directly at gsve...@mozilla.com about this issue since I'm in charge of Firefox crash reporting machinery. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1845205/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1845205] [NEW] Cannot submit crash reports from firefox' "this tab crashed" page
Public bug reported: Steps to reproduce: - Launch firefox - Enter "about:crashcontent" in the URL bar - Upon hitting return, the tab should crash and display the "This tab just crashed" page - Ensure that the checkmark to send the crash report is ticked - Add a comment (anything will do, a non-empty comment ensures that the crash is accepted by Mozilla crash reporting back-end) - Click on "Restore this tab" - Go to the "about:crashes" page Expected behaviour: In the "about:crashes" page the crash is displayed among the submitted crash reports, showing that the crash report was indeed submitted correctly. Actual behaviour: The crash appears among the unsubmitted crashes. This bug is specific to the packaged version of Firefox that comes with Ubuntu. I've tried reproducing using Mozilla's builds and crash submission works correctly there. See this bug https://bugzilla.mozilla.org/show_bug.cgi?id=1583247 on Mozilla's tracker regarding this behaviour. In Mozilla we noticed the issue because we've started properly processing crash reports coming from Ubuntu and tab crashes were strangely few. Feel free to contact me directly at gsve...@mozilla.com about this issue since I'm in charge of Firefox crash reporting machinery. ** Affects: firefox (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1845205 Title: Cannot submit crash reports from firefox' "this tab crashed" page Status in firefox package in Ubuntu: New Bug description: Steps to reproduce: - Launch firefox - Enter "about:crashcontent" in the URL bar - Upon hitting return, the tab should crash and display the "This tab just crashed" page - Ensure that the checkmark to send the crash report is ticked - Add a comment (anything will do, a non-empty comment ensures that the crash is accepted by Mozilla crash reporting back-end) - Click on "Restore this tab" - Go to the "about:crashes" page Expected behaviour: In the "about:crashes" page the crash is displayed among the submitted crash reports, showing that the crash report was indeed submitted correctly. Actual behaviour: The crash appears among the unsubmitted crashes. This bug is specific to the packaged version of Firefox that comes with Ubuntu. I've tried reproducing using Mozilla's builds and crash submission works correctly there. See this bug https://bugzilla.mozilla.org/show_bug.cgi?id=1583247 on Mozilla's tracker regarding this behaviour. In Mozilla we noticed the issue because we've started properly processing crash reports coming from Ubuntu and tab crashes were strangely few. Feel free to contact me directly at gsve...@mozilla.com about this issue since I'm in charge of Firefox crash reporting machinery. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1845205/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
