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

Electron crashed after print #19108

Closed
YiiGuxing opened this issue Jul 4, 2019 · 5 comments · Fixed by #19598
Closed

Electron crashed after print #19108

YiiGuxing opened this issue Jul 4, 2019 · 5 comments · Fixed by #19598

Comments

@YiiGuxing
Copy link

Version: v5.0.5, v5.0.6
JavaScript code: document.querySelector('iframe').contentWindow.print()

@MarshallOfSound MarshallOfSound added the blocked/need-info ❌ Cannot proceed without more information label Jul 4, 2019
@MarshallOfSound
Copy link
Member

Thanks for reaching out!

We require the template to be filled out on all new issues and pull requests. We do this so that we can be certain we have all the information we need to address your submission efficiently. This allows the maintainers to spend more time fixing bugs, implementing enhancements, and reviewing and merging pull requests.

Thanks for understanding and meeting us half way 😀

@YiiGuxing
Copy link
Author

YiiGuxing commented Jul 5, 2019

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:
    • 5.0.5
    • 5.0.6
  • Operating System:
    • Windows 10 1903 x64
  • Last Known Working Electron version:
    • 5.0.4

Expected Behavior

  1. Electron does not crash.
  2. Electron responds to UI events.

Actual Behavior

  1. Electron crashed.
  2. Electron does not respond to UI events.

To Reproduce

  1. $ git clone https://github.com/electron/electron-api-demos.git
  2. Modify package.json: "electron": "^5.0.1" -> "electron": "^5.0.6"
  3. $ npm install
  4. Add a button to index.html: <button onclick="window.print()">Print</button>
  5. $ npm run dev
  6. Click the print button
    • Click the print button on the dialog: Electron crashed after print.
    • Click the cancel button on the dialog: Electron does not respond to UI events after the dialog closes.

Screenshots

screenshot1
screenshot2

@lesleyandreza
Copy link

I have the same problem in MacOS Mojave 10.14.5.
With me the error happens in versions 5 and 6.
And when I tested in version 7.0.0-nightly.20190704 the print feature worked correctly.

Already corrected and missing to release in stable version?

@sofianguy sofianguy added this to Unsorted Issues in 6.1.x Jul 10, 2019
@sofianguy sofianguy added this to Unsorted Issues in 5.0.x Jul 10, 2019
@sofianguy sofianguy moved this from Unsorted Issues to Does Not Block Stable in 6.1.x Jul 15, 2019
@christophpre
Copy link

christophpre commented Jul 16, 2019

I can confirm this bug as well. Seems to have been introduced with 5.0.5 (maybe #18804). Print works for me with Version 5.0.4 and doesn't with 5.0.5 / 5.0.6.

Win 10 (Version 1809)

@HaNdTriX
Copy link

HaNdTriX commented Aug 5, 2019

I can confirm this bug also on

OS: MacOS 10.x.x
Electron: 6.0.x
Error:

objc[69614]: Class FIFinderSyncExtensionHost is implemented in both /System/Library/PrivateFrameworks/FinderKit.framework/Versions/A/FinderKit (0x7fff9df513d8) and /System/Library/PrivateFrameworks/FileProvider.framework/OverrideBundles/FinderSyncCollaborationFileProviderOverride.bundle/Contents/MacOS/FinderSyncCollaborationFileProviderOverride (0x10de91f50). One of the two will be used. Which one is undefined.

@sofianguy sofianguy moved this from Does Not Block Stable to Fixed for Next Release in 6.1.x Aug 7, 2019
@sofianguy sofianguy moved this from Unsorted Issues to Fixed for Next Release in 5.0.x Aug 7, 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 for Next Release
6.1.x
Fixed for Next Release
Development

Successfully merging a pull request may close this issue.

6 participants