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

after switching to WebContentsView the app crashes #42131

Open
3 tasks done
IroniumStudios opened this issue May 12, 2024 · 4 comments
Open
3 tasks done

after switching to WebContentsView the app crashes #42131

IroniumStudios opened this issue May 12, 2024 · 4 comments

Comments

@IroniumStudios
Copy link

Preflight Checklist

Electron Version

30.0.3

What operating system are you using?

Windows

Operating System Version

windows 11 23h2

What arch are you using?

x64

Last Known Working Electron version

None

Expected Behavior

Automate the Crashpad client to run seamlessly, preventing log errors and eliminating the risk of my app crashing unexpectedly.

Actual Behavior

During app navigation, sudden crashes occur with an error message indicating:
[17528:0512/115530.396:ERROR:crashpad_client_win.cc(868)] not connected
this issue could not be re created in electron fiddle

Testcase Gist URL

No response

Additional Information

No response

@codebytere
Copy link
Member

Could you please attach a crash dump to help us get more information? You can collect them by adding the following snippet to your main process code, before app.whenReady:

const { app, crashReporter } = require('electron')
console.log(app.getPath('crashDumps'))
crashReporter.start({ submitURL: '', uploadToServer: false })

Then reproduce the crash, zip up the crash dumps directory and attach it here.

@IroniumStudios
Copy link
Author

I can indeed add a crash dump, give me one moment

@IroniumStudios
Copy link
Author

IroniumStudios commented May 13, 2024

here is my provided crashpad files to help, the info on the crash is in the reports folder
Crashpad.zip

@ikapta
Copy link

ikapta commented May 23, 2024

I encountered the same issue, but I found that using removeChildView() before addChildView() can solve the current problem and avoid crashing.

  let current: WebContentsView | null = null;
  if (current) {
    contentView.removeChildView(current);
  }
  contentView.addChildView(newView);

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: 👍 Does Not Block Stable
Development

No branches or pull requests

3 participants