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

npm deasync cause crash in electron #95

Closed
pasqualevitale opened this issue Mar 12, 2018 · 2 comments
Closed

npm deasync cause crash in electron #95

pasqualevitale opened this issue Mar 12, 2018 · 2 comments

Comments

@pasqualevitale
Copy link

Environment: Windows 10 Pro (x64) and electron 1.7.9 (also 1.8.3 )

Problem description: The usage of "deasync" node module (version 0.1.11 and also 0.1.12) causes the crash of the renderer process.

In electron app, just using

var deasync = require('deasync')

as preload while creating BrowserWindow object, it cause the crash of the renderer.

The application crash randomically and also each time you come back from lock session: 1. run the application 2. lock session 3. unlock session 4. the renderer crash

I can also catch the crash event with

mainWindow.webContents.on('crashed', (event) => {
log.error( "crashed: ");
});

If use the require('deasync') into the main process the electron app crash drammatically and Window SO pop up is shown.

Any suggestions?

@yovanoc
Copy link

yovanoc commented Mar 17, 2018

I have the same problem:

const deasync = require('deasync')

console.log("a");

deasync.sleep(100)

console.log("b");

logs doesn't appear, even the "a" one !!!! and all my UI stay white .... if I remove the deasync.sleep line, all working great... but no sleep :/

@abbr
Copy link
Owner

abbr commented Aug 14, 2018

This is a issue of electron and deasync doesn't officially support electron. For reasons, see #81 or search other issues using keyword electron.

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

3 participants