You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Looks pretty similar to #32276, though I'm not able to reproduce the crash in 16.0.5 as the author of that issue claims.
Calling the print() API and providing undefined or null as the callback parameter still shows the dialog, although canceling that print dialog will still result in a crash (as documented in #32684). It's also worth noting that when running in Electron Fiddle, both the print dialog cancellation crash and this new crash share the same error code (3221225477), so I'm wondering if they're related, and if the PR fixing the dialog cancellation crash (#32632) might fix this as well.
The text was updated successfully, but these errors were encountered:
I actually just came across this error code without any printing workflow (Electron 16):
Exit status 3221225477
at EventEmitter.<anonymous> (C:\Program Files\nodejs\node_modules\npm\node_modules\npm-lifecycle\index.js:332:16)
at EventEmitter.emit (events.js:315:20)
at ChildProcess.<anonymous> (C:\Program Files\nodejs\node_modules\npm\node_modules\npm-lifecycle\lib\spawn.js:55:14)
at ChildProcess.emit (events.js:315:20)
at maybeClose (internal/child_process.js:1048:16)
at Process.ChildProcess._handle.onexit (internal/child_process.js:288:5)
Preflight Checklist
Electron Version
17.0.0
What operating system are you using?
Windows
Operating System Version
Windows 10 version 20H2
What arch are you using?
x64
Last Known Working Electron version
17.0.0-beta.2
Expected Behavior
Calling webContents.print({}, () => {}) will not crash, and will show the system print dialog.
Actual Behavior
The electron app crashes, even when the aforementioned print() call is encapsulated within a try-catch block.
Testcase Gist URL
https://gist.github.com/1ab968669f64a7707306e876ab2ff5bc
Additional Information
Looks pretty similar to #32276, though I'm not able to reproduce the crash in 16.0.5 as the author of that issue claims.
Calling the print() API and providing undefined or null as the callback parameter still shows the dialog, although canceling that print dialog will still result in a crash (as documented in #32684). It's also worth noting that when running in Electron Fiddle, both the print dialog cancellation crash and this new crash share the same error code (3221225477), so I'm wondering if they're related, and if the PR fixing the dialog cancellation crash (#32632) might fix this as well.
The text was updated successfully, but these errors were encountered: