Skip to content

Conversation

issackjohn
Copy link
Contributor

This pull request includes updates to the CrashReporting/AddStackToCrashReports.md file to improve the handling of stack frames in crash reports, particularly those involving extension scripts. The changes aim to enhance debugging while mitigating privacy concerns.

Key changes:

  • Replaced individual stack frames from extension scripts with <redacted> to preserve the rest of the call stack without revealing specific extension details.

closes #945

@issackjohn issackjohn changed the title [Call Stacks In Crash Reports] Per frame redaction [Call Stacks In Crash Reports] Per-frame redaction Mar 10, 2025
@issackjohn issackjohn marked this pull request as ready for review March 11, 2025 16:21
@issackjohn
Copy link
Contributor Author

@aluhrs13 @sethbrenith PTAL 😄

@aluhrs13 aluhrs13 merged commit f1d33ce into MicrosoftEdge:main Mar 12, 2025
1 check passed
@issackjohn issackjohn deleted the user/issackjohn/PerFrameRedaction branch March 27, 2025 21:07
@nicholaschen
Copy link

Just wondering, is this behavior going to be reproduced into Blink?

AFAICT the full stack trace is redacted https://chromium-review.googlesource.com/c/chromium/src/+/6203432 instead of the selected frames (unclear if this divergence is intentional).

@issackjohn
Copy link
Contributor Author

Yes, the per-frame redaction behavior has already landed in Blink. You can find the landed CL here: https://chromium-review.googlesource.com/c/chromium/src/+/6287916.

joone pushed a commit to joone/MSEdgeExplainers that referenced this pull request May 9, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[Call Stacks In Crash Reports] Redaction Levels
4 participants