Bug 1745224 Comment 0 Edit History

Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.

This bug is spun off from bug 1741287. It eventually became clear that bug 1741287 covers two distinct, unrelated bugs, as follows:

1. The build process for official builds sometimes fails to copy Mozilla-specific symbols for that build to the symbol server.

2. Sometimes the `debug_id` for Mozilla-specific modules (like XUL) is zeroed out in crash reports (perhaps only with content-process crashes). This prevents these modules from being symbolicated in those crash reports.

Bug 1741287 has now been DUPed to bug 1658531, which covers only issue #1. I'm opening this bug to deal with issue #2.

Neither issue exists on Windows. Issue #2 (this bug) may exist on Linux, though I haven't seen it. But I've seen many examples on macOS. So, at least for the moment, I'm limiting this report to macOS.

There's no way to search or facet on module debug ids. So it's difficult to search for crash reports that match this bug. At best you can search for bugs matching both issues #1 and #2, and look through them by hand to find examples of one or the other.

https://crash-stats.mozilla.org/search/?signature=~XUL%40&release_channel=nightly&release_channel=release&date=%3E%3D2021-12-02T17%3A36%3A00.000Z&date=%3C2021-12-09T17%3A36%3A00.000Z&_facets=signature&_facets=platform&_sort=-date&_columns=date&_columns=signature&_columns=product&_columns=version&_columns=build_id&_columns=platform#crash-reports

Here's the most recent example I can find for a mozilla-central nightly:

bp-756ce220-911c-41fc-b452-3b29c0211207

Here's a snippet from its "Modules" tab, showing Mozilla-specific modules with NULL debug ids:

          SafariSafeBrowsing   0.0.0.0  5513EB53B5393D8D801DE64175D3A03C0  SafariSafeBrowsing
        Ø libnss3.dylib        0.1.0.0  000000000000000000000000000000000  libnss3.dylib
        Ø libmozglue.dylib     0.1.0.0  000000000000000000000000000000000  libmozglue.dylib
          liblgpllibs.dylib    0.1.0.0  000000000000000000000000000000000  liblgpllibs.dylib
        Ø XUL  0.1.0.0         000000000000000000000000000000000  XUL
          libcorecrypto.dylib  0.1000.140.4  D211160DE22F344080541F5824519C7F0  libcorecrypto.dylib

This *may* be a bug in Breakpad code. When I have time I'll look through it for possible causes.
This bug is spun off from bug 1741287. It eventually became clear that bug 1741287 covers two distinct, unrelated bugs, as follows:

1. The build process for official builds sometimes fails to copy Mozilla-specific symbols for that build to the symbol server.

2. Sometimes the `debug_id` for Mozilla-specific modules (like XUL) is zeroed out in crash reports (perhaps only with content-process crashes). This prevents these modules from being symbolicated in those crash reports.

Bug 1741287 has now been DUPed to bug 1658531, which covers only issue #1. I'm opening this bug to deal with issue #2.

Neither issue exists on Windows. Issue #2 (this bug) may exist on Linux, though I haven't seen it. But I've seen many examples on macOS. So, at least for the moment, I'm limiting this report to macOS.

There's no way to search or facet on module debug ids. So it's difficult to search for crash reports that match this bug. At best you can search for bugs matching both issues #1 and #2, and look through them by hand to find examples of one or the other.

https://crash-stats.mozilla.org/search/?signature=~XUL%40&release_channel=nightly&release_channel=release&date=%3E%3D2021-12-02T17%3A36%3A00.000Z&date=%3C2021-12-09T17%3A36%3A00.000Z&_facets=signature&_facets=platform&_sort=-date&_columns=date&_columns=signature&_columns=product&_columns=version&_columns=build_id&_columns=platform#crash-reports

Here's the most recent example I can find for a mozilla-central nightly:

bp-756ce220-911c-41fc-b452-3b29c0211207

Here's a snippet from its "Modules" tab, showing Mozilla-specific modules with NULL debug ids:

          SafariSafeBrowsing   0.0.0.0       5513EB53B5393D8D801DE64175D3A03C0  SafariSafeBrowsing
        Ø libnss3.dylib        0.1.0.0       000000000000000000000000000000000  libnss3.dylib
        Ø libmozglue.dylib     0.1.0.0       000000000000000000000000000000000  libmozglue.dylib
          liblgpllibs.dylib    0.1.0.0       000000000000000000000000000000000  liblgpllibs.dylib
        Ø XUL                  0.1.0.0       000000000000000000000000000000000  XUL
          libcorecrypto.dylib  0.1000.140.4  D211160DE22F344080541F5824519C7F0  libcorecrypto.dylib

This *may* be a bug in Breakpad code. When I have time I'll look through it for possible causes.
This bug is spun off from bug 1741287. It eventually became clear that bug 1741287 covers two distinct, unrelated bugs, as follows:

1. The build process for official builds sometimes fails to copy Mozilla-specific symbols for that build to the symbol server.

2. Sometimes the `debug_id` for Mozilla-specific modules (like `XUL`) is zeroed out in crash reports (perhaps only with content-process crashes). This prevents these modules from being symbolicated in those crash reports.

Bug 1741287 has now been DUPed to bug 1658531, which covers only issue #1. I'm opening this bug to deal with issue #2.

Neither issue exists on Windows. Issue #2 (this bug) may exist on Linux, though I haven't seen it. But I've seen many examples on macOS. So, at least for the moment, I'm limiting this report to macOS.

There's no way to search or facet on module debug ids. So it's difficult to search for crash reports that match this bug. At best you can search for bugs matching both issues #1 and #2, and look through them by hand to find examples of one or the other.

https://crash-stats.mozilla.org/search/?signature=~XUL%40&release_channel=nightly&release_channel=release&date=%3E%3D2021-12-02T17%3A36%3A00.000Z&date=%3C2021-12-09T17%3A36%3A00.000Z&_facets=signature&_facets=platform&_sort=-date&_columns=date&_columns=signature&_columns=product&_columns=version&_columns=build_id&_columns=platform#crash-reports

Here's the most recent example I can find for a mozilla-central nightly:

bp-756ce220-911c-41fc-b452-3b29c0211207

Here's a snippet from its "Modules" tab, showing Mozilla-specific modules with NULL debug ids:

          SafariSafeBrowsing   0.0.0.0       5513EB53B5393D8D801DE64175D3A03C0  SafariSafeBrowsing
        Ø libnss3.dylib        0.1.0.0       000000000000000000000000000000000  libnss3.dylib
        Ø libmozglue.dylib     0.1.0.0       000000000000000000000000000000000  libmozglue.dylib
          liblgpllibs.dylib    0.1.0.0       000000000000000000000000000000000  liblgpllibs.dylib
        Ø XUL                  0.1.0.0       000000000000000000000000000000000  XUL
          libcorecrypto.dylib  0.1000.140.4  D211160DE22F344080541F5824519C7F0  libcorecrypto.dylib

This *may* be a bug in Breakpad code. When I have time I'll look through it for possible causes.

Back to Bug 1745224 Comment 0