-
Notifications
You must be signed in to change notification settings - Fork 11
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
critical memory leak #10
Comments
@FeelyChau only want to know if this critical issue will be fixed soon. I am not pushing, but I have a project to use this library, if it need long time to fix. I have to change to other way. |
@yiwiz-sai #12 Should fix it, but we still have some problems with testing that need to be fixed. But you could build it from this branch manually. |
thanks @FeelyChau ! I think this is a very critical bug, so once you finish the fix, will you release a new version to npmjs quickly? |
@FeelyChau I built and tested, it failed when I import any 3rd party python library
I know that commit failed to pass some tests, as you mentioned. I think the reason is it has some bugs about module import |
For this one, this is because you will need to use |
thanks @rickycao-qy, it works ! |
Would someone be able to approve the workflow run for #15 to see if it fixes the issues with the tests? Please and thank you. |
@rickycao-qy bip can not install python c-extension package,
hmm, seems ./bin/bip need miniconda, but I can not find miniconda in memory-leak branch I have to use tools/bip.js to install quickjs |
run it in docker, and run "docker stats" to watch the memory.
The text was updated successfully, but these errors were encountered: