Bug 210291 - Add null pointer checkings in WebFullScreenManager
Summary: Add null pointer checkings in WebFullScreenManager
Status: RESOLVED FIXED
Alias: None
Product: WebKit
Classification: Unclassified
Component: Media (show other bugs)
Version: WebKit Nightly Build
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: Peng Liu
URL:
Keywords: InRadar
Depends on:
Blocks:
 
Reported: 2020-04-09 11:05 PDT by Peng Liu
Modified: 2020-04-10 08:54 PDT (History)
3 users (show)

See Also:


Attachments
Patch (4.84 KB, patch)
2020-04-09 11:11 PDT, Peng Liu
dbates: review+
Details | Formatted Diff | Diff
Patch for landing (4.47 KB, patch)
2020-04-09 22:20 PDT, Peng Liu
no flags Details | Formatted Diff | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Peng Liu 2020-04-09 11:05:53 PDT
Add null pointer checking in WebFullScreenManager
Comment 1 Peng Liu 2020-04-09 11:07:28 PDT
<rdar://problem/54461890>
Comment 2 Peng Liu 2020-04-09 11:11:38 PDT
Created attachment 395977 [details]
Patch
Comment 3 Daniel Bates 2020-04-09 20:39:34 PDT
Comment on attachment 395977 [details]
Patch

View in context: https://bugs.webkit.org/attachment.cgi?id=395977&action=review

Patch looks good. A better patch would explain why this is being done in the change log description.

> Source/WebKit/WebProcess/FullScreen/WebFullScreenManager.cpp:54
> +    if (!element)

Ok as is. No change needed. Is the purpose of this change to workaround an unreproducible bug? Is so then the the optimal solution would include a FIXME comment explaining this/referencing the bug for the root cause fix. If not, then The optimal solution is to remove the assert.

Same comment for all changes below.
Comment 4 Peng Liu 2020-04-09 20:56:16 PDT
Comment on attachment 395977 [details]
Patch

View in context: https://bugs.webkit.org/attachment.cgi?id=395977&action=review

>> Source/WebKit/WebProcess/FullScreen/WebFullScreenManager.cpp:54
>> +    if (!element)
> 
> Ok as is. No change needed. Is the purpose of this change to workaround an unreproducible bug? Is so then the the optimal solution would include a FIXME comment explaining this/referencing the bug for the root cause fix. If not, then The optimal solution is to remove the assert.
> 
> Same comment for all changes below.

Thanks for the review.
Right, this patch is to fix a hard to reproduce crash.
Comment 5 Peng Liu 2020-04-09 22:20:29 PDT
Created attachment 396047 [details]
Patch for landing
Comment 6 EWS 2020-04-10 08:54:56 PDT
Committed r259874: <https://trac.webkit.org/changeset/259874>

All reviewed patches have been landed. Closing bug and clearing flags on attachment 396047 [details].