Closed Bug 1931237 Opened 4 days ago Closed 3 days ago

debug_file in stack traces written by minidump-analyzer on Linux have full filepaths rather than the basename

Categories

(Toolkit :: Crash Reporting, defect)

Unspecified
Linux
defect

Tracking

()

RESOLVED FIXED
134 Branch
Tracking Status
firefox-esr115 --- unaffected
firefox-esr128 --- unaffected
firefox132 --- wontfix
firefox133 --- fixed
firefox134 --- fixed

People

(Reporter: afranchuk, Assigned: afranchuk)

References

(Regression)

Details

(Keywords: regression)

Attachments

(2 files)

Telemetry shows this coincides with the new minidump-analyzer landing in bug 1743983. This seems to only affect Linux: other platforms only have the base filename. This was discovered because the symbolication server rejects the debug_files if they are the full paths.

The minidump-analyzer doesn't change anything about the module debug file which comes from the rust-minidump crates, so the platform differences stem there. It's likely that this is a nuance of the rust-minidump implementation, and it should be find to strip away the resulting path to be the basename to match the old behavior.

Set release status flags based on info from the regressing bug 1743983

:afranchuk could you add a severity on this when you have a moment?

Flags: needinfo?(afranchuk)

S3 because this prevents us from symbolicating Linux crash ping stacks, but there is a workaround on the server side (taking the basename of the debug path). Otherwise I would say S2.

Severity: -- → S2
Flags: needinfo?(afranchuk)
Severity: S2 → S3

Fx133 goes to RC next week, with the final beta building tomorrow.
Though we can take an uplift patch once it's ready and see where it aligns

There is a simple fix, I will have a patch shortly once verified.

On Linux, the rust-minidump crates yield (at least in some cases) full
file paths to the debug files. On other platforms this doesn't seem to
be the case. Either way, for all platforms we ensure that the
debug_file field is only the basename.

Pushed by afranchuk@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/7624f85e0e84 Always use the basename of files stored in the debug_file field r=gsvelto
Status: ASSIGNED → RESOLVED
Closed: 3 days ago
Resolution: --- → FIXED
Target Milestone: --- → 134 Branch

The patch landed in nightly and beta is affected.
:afranchuk, is this bug important enough to require an uplift?

  • If yes, please nominate the patch for beta approval.
  • If no, please set status-firefox133 to wontfix.

For more information, please visit BugBot documentation.

Flags: needinfo?(afranchuk)

On Linux, the rust-minidump crates yield (at least in some cases) full
file paths to the debug files. On other platforms this doesn't seem to
be the case. Either way, for all platforms we ensure that the
debug_file field is only the basename.

Original Revision: https://phabricator.services.mozilla.com/D229015

Attachment #9437964 - Flags: approval-mozilla-beta?

beta Uplift Approval Request

  • User impact if declined: Linux user crashes go unnoticed.
  • Code covered by automated testing: no
  • Fix verified in Nightly: yes
  • Needs manual QE test: no
  • Steps to reproduce for manual QE testing: N/A
  • Risk associated with taking this patch: Low
  • Explanation of risk level: Changes internal details of stack trace information generated by minidump-analyzer. This will only help crash ingestion, which is currently broken by invalid values.
  • String changes made/needed: N/A
  • Is Android affected?: yes
Flags: needinfo?(afranchuk)
Attachment #9437964 - Flags: approval-mozilla-beta? → approval-mozilla-beta+
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: