UserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/54.0.2840.71 Safari/537.36

Steps to reproduce the problem:
1. Start Chrome with the `--remote-debugging-port=9222` option;

2. Issue the said method. I used `chrome-remote-interface inspect`[1] but any WebSocket client will do, for example `wscat`[2]:

        $ wscat -c ws://localhost:9222/devtools/page/7076eb2d-eace-4637-b982-6d34984eb69b
        connected (press CTRL+C to quit)
        > { "id": 42, "method": "CacheStorage.requestCacheNames", "params": {"securityOrigin": "https://*"}}
        < {"method":"Inspector.targetCrashed","params":{}}

   The same happens at least with `file://*` too.

[1]: https://github.com/cyrus-and/chrome-remote-interface
[2]: https://github.com/websockets/wscat

What is the expected behavior?
Not "Aw, Snap!".

What went wrong?
"Aw, Snap!".

Did this work before? N/A 

Chrome version: 56.0.2902.0 dev (64-bit)  Channel: dev
OS Version: Debian GNU/Linux 8
Flash Version: 

As a bonus, I was wondering what is the proper syntax of the `securityOrigin` method.

I read [4] and tried several things without luck, i.e., the method always returns an empty array:

    http://*
    *://*:*
    https://github.com
    https://github.com:443
    *

Thanks!

[4]: https://www.chromium.org/Home/chromium-security/prefer-secure-origins-for-powerful-new-features