RESOLVED FIXED 239400
Allow C API clients to get the WKProcessTerminationReason in processDidCrash functions, and use in WebKitTestRunner
https://bugs.webkit.org/show_bug.cgi?id=239400
Summary Allow C API clients to get the WKProcessTerminationReason in processDidCrash ...
Simon Fraser (smfr)
Reported 2022-04-15 13:02:35 PDT
Allow C API clients to get the WKProcessTerminationReason in processDidCrash functions, and use in WebKitTestRunner
Attachments
Patch (24.10 KB, patch)
2022-04-15 13:07 PDT, Simon Fraser (smfr)
ews-feeder: commit-queue-
Patch (25.07 KB, patch)
2022-04-15 14:00 PDT, Simon Fraser (smfr)
no flags
Simon Fraser (smfr)
Comment 1 2022-04-15 13:07:31 PDT
Simon Fraser (smfr)
Comment 2 2022-04-15 14:00:21 PDT
Sam Weinig
Comment 3 2022-04-15 15:38:20 PDT
Comment on attachment 457723 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=457723&action=review > Source/WebKit/UIProcess/API/C/WKContext.h:137 > + WKContextChildProcessDidCrashWithDetailsCallback networkProcessDidCrashWithDetails; How would a single one of these that gets passed a "process-kind" enum be?
Sam Weinig
Comment 4 2022-04-15 15:40:04 PDT
Comment on attachment 457723 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=457723&action=review >> Source/WebKit/UIProcess/API/C/WKContext.h:137 >> + WKContextChildProcessDidCrashWithDetailsCallback networkProcessDidCrashWithDetails; > > How would a single one of these that gets passed a "process-kind" enum be? Or better yet, since this seems to be a pattern, a single one that gets passed a new WKObjectRef (I think that is the base name) "crash info" object that has some functions to grab the pid/reason?
Simon Fraser (smfr)
Comment 5 2022-04-15 18:06:18 PDT
Both good suggestions, but is it really worth spending effort polishing the legacy C SPI?
Simon Fraser (smfr)
Comment 6 2022-04-15 18:43:13 PDT
Alternatively we could replace this with Objective-C SPI
Sam Weinig
Comment 7 2022-04-17 15:15:59 PDT
(In reply to Simon Fraser (smfr) from comment #5) > Both good suggestions, but is it really worth spending effort polishing the > legacy C SPI? I was thinking of it not as polish but as just more ergonomical for going forward, since we don't really have a path off of it. (In reply to Simon Fraser (smfr) from comment #6) > Alternatively we could replace this with Objective-C SPI Isn't this used by the non-cocoa ports as well?
EWS
Comment 8 2022-04-18 14:21:35 PDT
Committed r292970 (249733@main): <https://commits.webkit.org/249733@main> All reviewed patches have been landed. Closing bug and clearing flags on attachment 457723 [details].
Radar WebKit Bug Importer
Comment 9 2022-04-18 14:22:15 PDT
Note You need to log in before you can comment on or make changes to this bug.