-
Notifications
You must be signed in to change notification settings - Fork 462
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 inside napi_is_detached_arraybuffer after period of no usage #1610
Comments
|
My thought was that the I recently experienced a slightly different stackdump which has a v8 call in the mix in case it helps.
Honestly, I'm not sure how to get a coredump when I hit this error, since it's happening inside the napi code that was called from javascript. |
What I meant is that Would you mind sharing the platform you encounter this problem? Windows, or macOS/Linux? |
Aha, I was reading the stack trace backwards and was thinking it showed Napi::ObjectWrap::ConstructorCallbackWrapper was calling into napi_is_detached_arraybuffer, not the other way around. macOS monterey 12.7.6 |
I have an Electron app which uses node-addon-api to retrieve and access a number of objects written in C++. After the app has been running for a long time and not received further usage (typically 12+ hours), it often will crash when I attempt to use it again. I suspect something is being garbage collected (the exported class?) during this period of no usage, so trying to access it later is what causes the crash.
I have collected a number of stack traces, but this is a good one since it should be just calling a static method with an int.
My related code:
.. and in the module init file:
Any insight or help would be appreciated, and let me know if you believe this is an issue for Electron instead.
Thanks!
The text was updated successfully, but these errors were encountered: