-
Notifications
You must be signed in to change notification settings - Fork 31
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
Crash on debugging #25
Comments
I found this: which seems identical, yet this still seems to be occurring. I've tried building canvas myself directly and the same occurs. |
See Automattic/node-canvas#855. The fix was merged but it hasn't been released yet. |
I see that bug was last commented on in Dec 2016 ??? / then a confirmation in July. It seems to related to 1.6.6, while the release is now 1.6.7 |
https://github.com/zbjornson/node-canvas/tree/prototype-fix Grabbed a copy of this branch, and rebuilt, seems to fix it. |
@john-terraspace all of the releases listed on the releases page are in npm -- |
Thanks for that, I'll remember that in future, the custom build worked perfectly, just need it for debugging purposes anyway and will switch to the normal release once done. Thanks |
As soon as a breakpoint is set in the node.js process the native canvas module crashes with the following error:
Microsoft Visual C++ Runtime Library
Assertion failed!
Program: ...s\canvas-prebuilt\canvas\build\Release\canvas.node
File: c:\projects\node-canvas-prebuilt\no...\nan_obj..._wrap.h
Line: 33
Expression: object->InternalFieldCount() > 0
For information on how your program can cause an assertion
failure, see the Visual C++ documentation on asserts
(Press Retry to debug the application - JIT must be enabled)
Abort Retry Ignore
Running latest via npm install and npm rebuild
node version 8.5.0
on Windows 10 Pro 64bit
The text was updated successfully, but these errors were encountered: