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

Remove iframe node from <webview> will cause webview crash. #18788

Closed
3 tasks done
cloudsere opened this issue Jun 14, 2019 · 5 comments
Closed
3 tasks done

Remove iframe node from <webview> will cause webview crash. #18788

cloudsere opened this issue Jun 14, 2019 · 5 comments

Comments

@cloudsere
Copy link

Preflight Checklist

  • I have read the Contributing Guidelines for this project.
  • I agree to follow the Code of Conduct that this project adheres to.
  • I have searched the issue tracker for an issue that matches the one I want to file, without success.

Issue Details

  • Electron Version:
    • v5.0.2
  • Operating System:
    • macOS 10.13.6
  • Last Known Working Electron version:
    • Haven't tried on other electron versions.

Expected Behavior

I have an app which runs in electron <webview>. I need to render multiple iframes inside this <webview> and dynamic add or remove them.

Actual Behavior

When I remove one <iframe> from the dom tree, the whole <webview> crashes. I didn't use JS to remove iframe node, instead, I just delete one <iframe> from the dom inspector, and the <webview> crashes.

To Reproduce

This is an example : https://github.com/cloudsere/electron-quick-start. You can run commands below to reproduce.

$ git clone https://github.com/cloudsere/electron-quick-start
$ npm install
$ npm start
@alexstrat
Copy link
Contributor

alexstrat commented Jun 21, 2019

Here is a gist to be used in electron-fiddle to reproduce the issue:

Note that it does not seem that the webview itself has crashed (I can access DOM via DevTools) but rather that the repainting is getting blocked.

Tested with other versions:

  • 4.2.4: not reproduced
  • 5.0.5: reproduced
  • 5.0.4: reproduced
  • 6.0.0-beta.1: reproduced
  • 6.0.0-beta.2: not reproduced
  • 6.0.0-beta.9: not reproduced

@alexstrat
Copy link
Contributor

alexstrat commented Jun 21, 2019

Relates, or even duplicates #17890

@alexstrat
Copy link
Contributor

The fact that the bug is not reproduced with 6.0.0-beta.2 whereas it was present beta.1 is a sign that there is a fix hiding in the diff Chrome 76.0.3774.1 => 76.0.3783.1.

This one is a good candidate: https://chromium.googlesource.com/chromium/src/+/7464a6b4e3cf91dd1eb96d922736f0815b94ed9c%5E%21/#F3

@cloudsere
Copy link
Author

The fact that the bug is not reproduced with 6.0.0-beta.2 whereas it was present beta.1 is a sign that there is a fix hiding in the diff Chrome 76.0.3774.1 => 76.0.3783.1.

This one is a good candidate: https://chromium.googlesource.com/chromium/src/+/7464a6b4e3cf91dd1eb96d922736f0815b94ed9c%5E%21/#F3

Thank you , this fix works!

@sofianguy
Copy link
Contributor

fixed #18976

@sofianguy sofianguy moved this from Unsorted Issues to Fixed in 5.0.7 in 5.0.x Jul 16, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
No open projects
5.0.x
Fixed in 5.0.7
Development

No branches or pull requests

3 participants