Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

[cgo] unloadLibrary is never called

Open
#133 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
go
Domain
tooling

Research direction

Start by tracing the cgo wrapper lifecycle and locating the wrapper destructor and unloadLibrary entry points. Determine how destruction is handled and verify that the library is unloaded when the wrapper is released; the issue provides no named files or tests.

Written by the indexing model from the issue text.

Description

We would need to call unload library with the wrapper destructor, but I am a bit helpless how this works. @qmuntal: Is there a chance you can take a look at this?

Dominant language
Go
Stars
54
Forks
26
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from Autodesk/AutomaticComponentToolkit

All issues in Autodesk/AutomaticComponentToolkit

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.