(In reply to Jonathan Kew [:jfkthame] from comment #1) > Looking at the current crash reports, there are a couple of pairs that look like they might be the same user making two attempts to print something, and crashing both times; if so, perhaps there's hope that we'll get a bug report with a specific page/document that reproduces this. meta-note: none of these crash reports were submitted with a URL-of-the-page-that-was-loaded. I assume that's because these are all parent-process crashes, and the parent process isn't specific to any one page/URL. Maybe when we enter `PContentParent::OnMessageReceived` or somesuch, we should make a note of the content process's URL for usage in possible crash reports, in the event that there's a crash? (if the user checks the box in the crash-report dialog to include the URL of the crashing content) I'm not sure whether that's something that's already supposed to just work.
Bug 1901043 Comment 5 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
(In reply to Jonathan Kew [:jfkthame] from comment #1) > Looking at the current crash reports, there are a couple of pairs that look like they might be the same user making two attempts to print something, and crashing both times; if so, perhaps there's hope that we'll get a bug report with a specific page/document that reproduces this. meta-note: none of this bug's associated crash reports were submitted with a URL-of-the-page-that-was-loaded. I assume that's because these are all parent-process crashes, and the parent process isn't specific to any one page/URL. Maybe when we enter `PContentParent::OnMessageReceived` or somesuch, we should make a note of the content process's URL for usage in possible crash reports, in the event that there's a crash? (if the user checks the box in the crash-report dialog to include the URL of the crashing content) I'm not sure whether that's something that's already supposed to just work.