Skip to content
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

Linux: out# results hidden after call to println!() #16

Closed
kurtlawrence opened this issue Mar 14, 2019 · 1 comment
Closed

Linux: out# results hidden after call to println!() #16

kurtlawrence opened this issue Mar 14, 2019 · 1 comment
Assignees
Labels
bug Something isn't working

Comments

@kurtlawrence
Copy link
Owner

eg

papyrus=> 5+6
papyrus [out0]: 11
papyrus=> println!("adf")
papyrus [out1]: ()
papyrus=> 8+9
papyrus [out2]: ()

might be related to #15, the out2 should be 17

@kurtlawrence kurtlawrence added the bug Something isn't working label Mar 14, 2019
@kurtlawrence kurtlawrence self-assigned this Mar 14, 2019
@kurtlawrence
Copy link
Owner Author

fixed in 0441e5b

This issue was a little subtle to work out. Basically the api function dlopen will keep loaded libraries in memory to avoid continuously allocating memory. It only does not release the library when thread_local data is hanging around, and it seems println!() is something that does this. Hence to avoid not having the library not updated with a new new() call, the library is renamed and a different lib name is passed to the function. This is very annoying as it has needless fs interactions and a growing fs footprint but what can you do ¯_(ツ)_/¯

see:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant