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.

Sign up for GitHub

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

Jump to bottom

Properly figure out destructing a Module. #19

Open
hainesr opened this issue Apr 7, 2019 · 0 comments
Open

Properly figure out destructing a Module. #19

hainesr opened this issue Apr 7, 2019 · 0 comments
Assignees
@hainesr
Labels
bug Something isn't working enhancement New feature or request
Milestone
1.0.0

Comments

@hainesr
Copy link
Owner

hainesr commented Apr 7, 2019

The Module::open method is safe when a block is passed: #close is called when the block exits. But if no block is passed, or Module::new is used then there's the potential for memory leaks if the underlying C memory structures are not cleared explicitly.

Ruby "destructor" info here: https://stackoverflow.com/questions/5956067/ruby-destructors
@hainesr hainesr added bug Something isn't working enhancement New feature or request labels Apr 7, 2019
@hainesr hainesr added this to the 1.0.0 milestone Apr 7, 2019
@hainesr hainesr self-assigned this Apr 7, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@hainesr hainesr

Labels
bug Something isn't working enhancement New feature or request
Projects
None yet
Milestone
1.0.0
Development

No branches or pull requests
1 participant
@hainesr