fix(tusb_cdc): Added freeing cdc object #105
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Common sequence for tinyusb CDC driver install:
tinyusb_driver_install()
tusb_cdc_acm_initialized()
tusb_cdc_acm_init()
During the
tusb_cdc_acm_init()
the internal objectcdc_inst->subclass_obj
is allocated.And doesn't freeing during the common uninstall:
tusb_cdc_acm_deinit()
tinyusb_driver_uninstall()
Changes
obj_free(itf)
, which is the freeing mechanism for functionalloc_obj(itf)
obj_free(itf)
call whiletusb_cdc_acm_deinit()
And during these steps there is no freeing present.
Related
Testing
Checklist
Before submitting a Pull Request, please ensure the following: