-
Notifications
You must be signed in to change notification settings - Fork 3.9k
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
Quiet crash when using native modules #37
Comments
Issue still present in node-webkit 0.2.4. |
Fixed in 0.2.5 |
I've tested a couple modules with 0.2.5 (on linux x64) - node-buffertools and node-leveldb seem to work now, but I still get the same symptoms when trying to use node-bignum. :( Test case: |
Confirmed, I'll looking into it. |
also happening on windows x86. node modules with native bindings, originally it was throwing error because of the node x64 modules, but now running and recompiled for node 0.8.9 x86 I just get a grey window and no errors in the devtools etc. Devtools network tab says it is downloading my main js file (which does the includes) modules I am using are ffi and ref. What version of node is this built against? maybe I just need to recompile with whichever node headers node-webkit expects? Just tried recompiling my modules with node 8.8 (i think that is the one that node-webkit 0.2.5 uses) but still same grey screen. |
It seems node-webkit has problems of using native modules on Windows platform, I opened a new issue #47 for this one, it will be fixed in v0.2.6. |
@justmoon the OpenSSL's symbols are not exported, which caused failing of bignum module, I'll fix it in v0.2.6. |
The following app stop executing without any error message whatsoever:
https://gist.github.com/3508168
The native module is loaded fine (
require('buffertools');
), but when you use it, execution simply stops. The only other visible symptom is that the node-webkit window is grey instead of white. There are no log messages or errors of any kind.Tested on Linux x64, node-webkit 0.2.3.
Edit: Looks like this affects all native modules for me. Loading them works fine, but once you try to call any of their methods, the above bug is triggered.
The text was updated successfully, but these errors were encountered: