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

NWJS framework crash with fatal error in , line 0 unimplemented code #6335

Closed
asleepysamurai opened this issue Dec 16, 2017 · 6 comments
Closed

Comments

@asleepysamurai
Copy link

asleepysamurai commented Dec 16, 2017

NWJS Version : 0.27.2 (SDK)
Operating System : OSX El Capitan (10.11.4)

Expected behavior

NWJS Framework should not crash

Actual behavior

NWJS Framework (thread 0) crashes with following message:

#
# Fatal error in , line 0
# unimplemented code
#

This happens only when I'm running the code in a child process obtained with child_process.fork.

How to reproduce

Unfortunately, I cannot provide the exact code which triggers this, but I have attached the crash dump which says that the nwjs framework thread 0 crashed with EXC_BAD_INSTRUCTION / EXC_I386_INVOP.

Crash Dump:
https://filebin.ca/3ksfOpZAqRQ4/712953f3-6432-49f5-a79f-200dcb289bb2.dmp

Minidump_stackwalk output (It doesnt seem to be able to find the symbol files even though I've placed them correctly. Not sure whats happening there)
minidump_stackwalk.txt

@rogerwang
Copy link
Member

Thanks for reporting. Does it reproduce with 0.27.1 and 0.26.6?

@asleepysamurai
Copy link
Author

asleepysamurai commented Dec 16, 2017

It's reproducible in 0.27.1 but not in 0.26.6.

As a temp workaround, I'm going to downgrade to 0.26.6.

EDIT: Accidentally closed and had to reopen the issue. Sorry about that.

@Christywl
Copy link
Contributor

I also reproduce this error on Linux with nwjs-sdk-v0.27.2.
Launch the app and then close it, you can see this error in the terminal:

#
# Fatal error in , line 0
# unimplemented code
#

index.html:
<script src='parent.js'></script>

parent.js:

const cp = require('child_process');
const n = cp.fork('sub.js');

n.on('message', (m) => {
  console.log('PARENT got message:', m);
});

n.send({ hello: 'world' });

sub.js:

process.on('message', (m) => {
  console.log('CHILD got message:', m);
});
process.send({ foo: 'bar', baz: NaN });

@rogerwang
Copy link
Member

@Christywl does it reproduce with this build: https://dl.nwjs.io/live-build/12-20-2017/nw27-44f34c0-c520573-4f2dbdc-f13e613/v0.27.3/

We fixed a similar issue yesterday in this build.

@Christywl
Copy link
Contributor

Christywl commented Dec 20, 2017

@rogerwang , this error still appears in this nightly build.

@rogerwang
Copy link
Member

This is fixed in git and will be available in the next nightly build.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants