Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Renderer process crash: Terminating renderer for bad IPC message, reason 95 #7001

Closed
hkaya opened this issue Mar 5, 2019 · 5 comments
Closed

Comments

@hkaya
Copy link

hkaya commented Mar 5, 2019

Hi,

I'm seeing a strange renderer crash after upgrading from 0.24 to 0.36. I confirmed the same behavior on 0.36.1, 0.36.4 and 0.37.0 sdk builds.

Webview processes that make XHR requests are crashing with the following error message:

[92800:92808:0305/145204.806109:ERROR:bad_message.cc(27)] Terminating renderer for bad IPC message, reason 95

The issue is almost identical to #6197, except changing accessible_resources doesn't help in my case.

Here is a test app I use to reproduce the issue: https://gist.github.com/hkaya/b938a6263899a5b5aac01860841a52dd

You need to update this line: https://gist.github.com/hkaya/b938a6263899a5b5aac01860841a52dd#file-index-html-L9

Thank you!

@rogerwang
Copy link
Member

The crash is due to file:// url cannot be used in origin header of CORS request:

https://cs.chromium.org/chromium/src/content/browser/loader/resource_dispatcher_host_impl.cc?sq=package:chromium&g=0&l=2185

It will work If the code is changed to chrome-extension URL in line 16 by simply using 'id' rather than 'base + id'.

@hkaya
Copy link
Author

hkaya commented Mar 6, 2019

Thank you for quickly getting back to me Roger. This makes sense however I still think that file:// origins should be allowed especially since I’m setting the disable-web-security flag. This behavior also prevents loading webpages from another directory.

@rogerwang
Copy link
Member

@hkaya you are right. I'll fix this under that flag. Thanks.

@rogerwang
Copy link
Member

This is fixed in git and will be available in the next nightly build.

@hkaya
Copy link
Author

hkaya commented Mar 7, 2019

@rogerwang the fix is working. Thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants