[Webkit-unassigned] [Bug 147227] Crash in WebPlatformStrategies::createPingHandle - Deref a null NetworkingContext

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=147227

Alexey Proskuryakov <ap at webkit.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
 Attachment #257354|review?                     |review+
              Flags|                            |

--- Comment #3 from Alexey Proskuryakov <ap at webkit.org> ---
Comment on attachment 257354
  --> https://bugs.webkit.org/attachment.cgi?id=257354
Patch v1

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

Hrmpf. Nice.

> LayoutTests/http/tests/security/contentSecurityPolicy/user-style-sheet-font-crasher-expected.txt:3
> +CONSOLE MESSAGE: Refused to load the font 'http://127.0.0.1:8000/security/contentSecurityPolicy/example_font.woff' because it violates the following Content Security Policy directive: "font-src http://webkit.org".
> +
> +CONSOLE MESSAGE: Refused to load the font 'http://127.0.0.1:8000/security/contentSecurityPolicy/example_font.woff' because it violates the following Content Security Policy directive: "font-src http://webkit.org".

Why is this logged twice, do we have a bug?

> LayoutTests/http/tests/security/contentSecurityPolicy/user-style-sheet-font-crasher.html:8
> +    testRunner.addUserStyleSheet("@font-face { font-family: ExampleFont; src: url(example_font.woff); }", true);

I wonder if this can also be reproduced with something like

<iframe src="http://www.apple.com"></iframe>
<script>
frames[0].document.write(theStylesheet);
</script>

> Source/WebKit2/WebProcess/WebCoreSupport/WebPlatformStrategies.cpp:255
> +    // We shouldn't be sending ping loads during that process anyways.

What do other browsers do? I wonder if "shouldn't" may be too assertive.

It feels like we shouldn't apply user stylesheets in initial documents, what do you think?

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.webkit.org/pipermail/webkit-unassigned/attachments/20150723/60bee52c/attachment.html>