You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What happened: While running a packaged Node.js application that includes the sizeof package, the application encountered an unknown issue, resulting in unexpected termination or stoppage.
What you expected to happen: I expected the packaged application to run without errors, just as it does when not packaged with Nexe.
How to reproduce it (as minimally and precisely as possible):
Package a Node.js application using Nexe.
Include the sizeof package in the application.
create a object stack and keep increasing its size with random data
use sizeof functionality to determine the object's size on realtime
Attempt to run the packaged application.
Anything else we need to know?:
The issue occurs specifically when the sizeof package is included in the packaged application, implementation before sizeof was included it was working fine after packaging.
No error messages or logs were generated, making it challenging to identify the root cause of the problem.
Environment:
Platform(OS/Version): WIndows 10
Host Node Version: 16.13.2
Target Node Version: 16.13.2
Nexe version: nexe@4.0.0-rc.1
The text was updated successfully, but these errors were encountered:
What happened: While running a packaged Node.js application that includes the sizeof package, the application encountered an unknown issue, resulting in unexpected termination or stoppage.
What you expected to happen: I expected the packaged application to run without errors, just as it does when not packaged with Nexe.
How to reproduce it (as minimally and precisely as possible):
Package a Node.js application using Nexe.
Include the sizeof package in the application.
create a object stack and keep increasing its size with random data
use sizeof functionality to determine the object's size on realtime
Attempt to run the packaged application.
Anything else we need to know?:
The issue occurs specifically when the sizeof package is included in the packaged application, implementation before sizeof was included it was working fine after packaging.
No error messages or logs were generated, making it challenging to identify the root cause of the problem.
Environment:
The text was updated successfully, but these errors were encountered: