-
Notifications
You must be signed in to change notification settings - Fork 24
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
HUGE off-heap memory leak and heap memory leak when using quick-js #61
Comments
And seems is the bug from quack which introduced by Javascript-Expansion 2.x, so I will try to use 1.x to see if it fixed it. |
Confirmed this with our testing. We were leaking 650mb/s at one point. Removing QuickJS solved it. We never had a heap memory leak, only native. |
@sandtechnology I don't know a whole lot of c++ but I saw there is a fork of quack that seems better maintained. If you understand it, can you check this fork to see if it looks like it fixes the problem? https://github.com/uk-taniyama/quack |
I just implemented another possible engine to use called RhinoJS. I'm not entirely sure what all it offers but I tested basic script evaluations which seemed to work fine. I have a copy of the jar in this open PR #65 |
Not sure if the issue from quick-js or your side, but I post them to remind other server owner when troubleshooting.
Heap memory leak by mat report:
Merged path2gc shows it was referred by JNI Gobal ref:
Also off-heap having LARGE leak about 50GB+, jmap shows there are lots of JNI refs
The text was updated successfully, but these errors were encountered: