WebKit Bugzilla
New
Browse
Log In
×
Sign in with GitHub
or
Remember my login
Create Account
·
Forgot Password
Forgotten password account recovery
RESOLVED FIXED
190738
[EME] Fix crash during tracing in gst_qtdemux_request_protection_context
https://bugs.webkit.org/show_bug.cgi?id=190738
Summary
[EME] Fix crash during tracing in gst_qtdemux_request_protection_context
Charlie Turner
Reported
2018-10-18 15:07:31 PDT
And update new clearkey baselines.
Attachments
Patch
(40.93 KB, patch)
2018-10-19 03:10 PDT
,
Charlie Turner
no flags
Details
Formatted Diff
Diff
Patch
(47.07 KB, patch)
2018-10-19 03:17 PDT
,
Charlie Turner
no flags
Details
Formatted Diff
Diff
Patch
(47.15 KB, patch)
2018-10-19 03:21 PDT
,
Charlie Turner
no flags
Details
Formatted Diff
Diff
Patch
(48.13 KB, patch)
2018-10-19 04:54 PDT
,
Charlie Turner
no flags
Details
Formatted Diff
Diff
Patch for landing
(46.62 KB, patch)
2018-10-19 09:41 PDT
,
Charlie Turner
no flags
Details
Formatted Diff
Diff
Patch for landing
(46.64 KB, patch)
2018-10-19 09:46 PDT
,
Charlie Turner
no flags
Details
Formatted Diff
Diff
Show Obsolete
(5)
View All
Add attachment
proposed patch, testcase, etc.
Charlie Turner
Comment 1
2018-10-19 03:10:08 PDT
Created
attachment 352776
[details]
Patch
Charlie Turner
Comment 2
2018-10-19 03:17:18 PDT
Created
attachment 352777
[details]
Patch
Charlie Turner
Comment 3
2018-10-19 03:21:18 PDT
Created
attachment 352778
[details]
Patch Rebase over master
Charlie Turner
Comment 4
2018-10-19 04:54:53 PDT
Created
attachment 352781
[details]
Patch
Xabier Rodríguez Calvar
Comment 5
2018-10-19 05:10:45 PDT
Comment on
attachment 352781
[details]
Patch View in context:
https://bugs.webkit.org/attachment.cgi?id=352781&action=review
> LayoutTests/platform/gtk/imported/w3c/web-platform-tests/encrypted-media/resources/clearkey-retrieve-destroy-persistent-license-expected.txt:10 > +layer at (0,0) size 800x600 > + RenderView at (0,0) size 800x600 > +layer at (0,0) size 800x120 > + RenderBlock {HTML} at (0,0) size 800x120 > + RenderBody {BODY} at (8,8) size 784x104 > + RenderBlock {DIV} at (0,0) size 784x0 > + RenderBlock {DIV} at (0,0) size 784x104 > + RenderText {#text} at (0,0) size 0x0 > +layer at (8,8) size 200x100 > + RenderVideo {VIDEO} at (0,0) size 200x100
why are we getting the tree dump here?
> LayoutTests/platform/gtk/imported/w3c/web-platform-tests/encrypted-media/resources/clearkey-retrieve-persistent-license-expected.txt:10 > +layer at (0,0) size 800x600 > + RenderView at (0,0) size 800x600 > +layer at (0,0) size 800x120 > + RenderBlock {HTML} at (0,0) size 800x120 > + RenderBody {BODY} at (8,8) size 784x104 > + RenderBlock {DIV} at (0,0) size 784x0 > + RenderBlock {DIV} at (0,0) size 784x104 > + RenderText {#text} at (0,0) size 0x0 > +layer at (8,8) size 200x100 > + RenderVideo {VIDEO} at (0,0) size 200x100
ditto
Charlie Turner
Comment 6
2018-10-19 05:14:59 PDT
> why are we getting the tree dump here?
I don't know, it was generated from the run-webkit-tests script, which I was invoking like run-webkit-tests --gtk --debug --test-list=$(fd '.*clearkey.*.html')
Xabier Rodríguez Calvar
Comment 7
2018-10-19 06:20:24 PDT
Comment on
attachment 352781
[details]
Patch (In reply to Charlie Turner from
comment #6
)
> > why are we getting the tree dump here? > > I don't know, it was generated from the run-webkit-tests script, which I was > invoking like run-webkit-tests --gtk --debug --test-list=$(fd > '.*clearkey.*.html')
Then I think we should remove both these expectations and flag them because they shouldn't have a tree dump.
Charlie Turner
Comment 8
2018-10-19 09:41:08 PDT
Created
attachment 352790
[details]
Patch for landing
Charlie Turner
Comment 9
2018-10-19 09:42:48 PDT
(In reply to Xabier Rodríguez Calvar from
comment #7
)
> Comment on
attachment 352781
[details]
> Patch > > (In reply to Charlie Turner from
comment #6
) > > > why are we getting the tree dump here? > > > > I don't know, it was generated from the run-webkit-tests script, which I was > > invoking like run-webkit-tests --gtk --debug --test-list=$(fd > > '.*clearkey.*.html') > > Then I think we should remove both these expectations and flag them because > they shouldn't have a tree dump.
To be clear, the following tests where producing dump render tree output for unknown reasons. For now these have been marked as [ Missing ] in this patch. platform/gtk/imported/w3c/web-platform-tests/encrypted-media/resources/clearkey-retrieve-destroy-persistent-license.html platform/gtk/imported/w3c/web-platform-tests/encrypted-media/resources/clearkey-retrieve-persistent-license.html
WebKit Commit Bot
Comment 10
2018-10-19 09:44:08 PDT
Comment on
attachment 352790
[details]
Patch for landing Rejecting
attachment 352790
[details]
from commit-queue. Failed to run "['/Volumes/Data/EWS/WebKit/Tools/Scripts/webkit-patch', '--status-host=webkit-queues.webkit.org', '--bot-id=webkit-cq-03', 'validate-changelog', '--check-oops', '--non-interactive', 352790, '--port=mac']" exit_code: 1 cwd: /Volumes/Data/EWS/WebKit ChangeLog entry in LayoutTests/ChangeLog contains OOPS!. Full output:
https://webkit-queues.webkit.org/results/9666562
Charlie Turner
Comment 11
2018-10-19 09:46:18 PDT
Created
attachment 352791
[details]
Patch for landing
WebKit Commit Bot
Comment 12
2018-10-19 10:25:46 PDT
Comment on
attachment 352791
[details]
Patch for landing Clearing flags on attachment: 352791 Committed
r237292
: <
https://trac.webkit.org/changeset/237292
>
WebKit Commit Bot
Comment 13
2018-10-19 10:25:48 PDT
All reviewed patches have been landed. Closing bug.
Ms2ger (he/him; ⌚ UTC+1/+2)
Comment 14
2018-10-22 00:07:54 PDT
(In reply to Charlie Turner from
comment #9
)
> (In reply to Xabier Rodríguez Calvar from
comment #7
) > > Comment on
attachment 352781
[details]
> > Patch > > > > (In reply to Charlie Turner from
comment #6
) > > > > why are we getting the tree dump here? > > > > > > I don't know, it was generated from the run-webkit-tests script, which I was > > > invoking like run-webkit-tests --gtk --debug --test-list=$(fd > > > '.*clearkey.*.html') > > > > Then I think we should remove both these expectations and flag them because > > they shouldn't have a tree dump. > > To be clear, the following tests where producing dump render tree output for > unknown reasons. For now these have been marked as [ Missing ] in this patch. > > > platform/gtk/imported/w3c/web-platform-tests/encrypted-media/resources/ > clearkey-retrieve-destroy-persistent-license.html > > platform/gtk/imported/w3c/web-platform-tests/encrypted-media/resources/ > clearkey-retrieve-persistent-license.html
That's because they're not tests, they're helper files.
Xabier Rodríguez Calvar
Comment 15
2018-10-22 01:50:41 PDT
(In reply to Ms2ger (he/him; ⌚ UTC+1/+2) from
comment #14
)> >
> > platform/gtk/imported/w3c/web-platform-tests/encrypted-media/resources/ > > clearkey-retrieve-destroy-persistent-license.html > > > > platform/gtk/imported/w3c/web-platform-tests/encrypted-media/resources/ > > clearkey-retrieve-persistent-license.html > > That's because they're not tests, they're helper files.
So should we then skip them instead?
Ms2ger (he/him; ⌚ UTC+1/+2)
Comment 16
2018-10-22 02:02:02 PDT
(In reply to Xabier Rodríguez Calvar from
comment #15
)
> (In reply to Ms2ger (he/him; ⌚ UTC+1/+2) from
comment #14
)> > > > > platform/gtk/imported/w3c/web-platform-tests/encrypted-media/resources/ > > > clearkey-retrieve-destroy-persistent-license.html > > > > > > platform/gtk/imported/w3c/web-platform-tests/encrypted-media/resources/ > > > clearkey-retrieve-persistent-license.html > > > > That's because they're not tests, they're helper files. > > So should we then skip them instead?
I think that makes the most sense, yes.
Miguel Gomez
Comment 17
2019-05-02 06:03:43 PDT
media/encrypted-media/clearKey/clearKey-webm-video-playback-mse.html was marked here as timeout, but it's passing reliably since
r244585
(it seems), so updating expctations.
Miguel Gomez
Comment 18
2019-05-02 06:46:32 PDT
media/encrypted-media/clearKey/clearKey-encrypted-webm-event-mse.html was marked failure here but since
r244585
it has started to pass. Updating expectations.
Note
You need to
log in
before you can comment on or make changes to this bug.
Top of Page
Format For Printing
XML
Clone This Bug