Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Spec should define a processing model #11

Open
clelland opened this issue Dec 17, 2020 · 2 comments · May be fixed by #19
Open

Spec should define a processing model #11

clelland opened this issue Dec 17, 2020 · 2 comments · May be fixed by #19

Comments

@clelland
Copy link
Collaborator

From w3c/reporting#169 (comment):

We should define some processing algorithm for each of the above? We describe what the reports are, but there is no guidance on processing.

This spec describes a report format, but no processing model for generating or sending them. That should be described in some amount of useful detail.

cc: @igrigorik
@pes10k
Copy link

pes10k commented Dec 17, 2020

I wonder if the proposers are familiar with this work, and if it has thoughts on how it could inform this proposal.

https://www.ndss-symposium.org/wp-content/uploads/2020/02/24428-paper.pdf

@clelland
Copy link
Collaborator Author

clelland commented Jul 4, 2024

It looks like that paper deals with sanitizing and anonymizing data from native call stacks and core dumps -- this proposal sends far less information, just reporting the fact that a crash occurred at all, with essentally no details about the running process other than a very coarse-grained reason for the crash. (And if the crash was due to a bug in native code, then there is no other information attached at all)

@clelland clelland linked a pull request Oct 25, 2024 that will close this issue
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Start adding processing model WICG/crash-reporting
2 participants
@clelland @pes10k