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

[BUG] Possible USB MIDI 2.0 Driver Memory Leak #505

Open
AmeNote-Michael opened this issue Feb 3, 2025 · 1 comment
Open

[BUG] Possible USB MIDI 2.0 Driver Memory Leak #505

AmeNote-Michael opened this issue Feb 3, 2025 · 1 comment
Assignees
@Psychlist1972
Labels
area-usb-driver 💻 Related to the USB MIDI 2.0 driver bug 🐞 Something isn't working fixed-awaiting-public-release 🕙 Fixed in our internal builds. Waiting to make its way to a public release.

Comments

@AmeNote-Michael
Copy link
Collaborator

Describe the bug
USBMIDI2DriverSelectInterface line 1065 does a return without freeing pSettingPairs, static analysis is flagging it as a potential memory leak.

Reported by @garydan42
@AmeNote-Michael AmeNote-Michael added the bug 🐞 Something isn't working label Feb 3, 2025
@AmeNote-Michael
Copy link
Collaborator Author

Resolved in pull request #506

@Psychlist1972 Psychlist1972 added the area-usb-driver 💻 Related to the USB MIDI 2.0 driver label Feb 3, 2025
@Psychlist1972 Psychlist1972 changed the title [BUG] Possible Memory Leak [BUG] Possible USB MIDI 2.0 Driver Memory Leak Feb 3, 2025
@Psychlist1972 Psychlist1972 added the fixed-awaiting-public-release 🕙 Fixed in our internal builds. Waiting to make its way to a public release. label Feb 9, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@Psychlist1972 Psychlist1972

Labels
area-usb-driver 💻 Related to the USB MIDI 2.0 driver bug 🐞 Something isn't working fixed-awaiting-public-release 🕙 Fixed in our internal builds. Waiting to make its way to a public release.
Projects
Windows MIDI Services
Status: No status
Milestone
No milestone
Development

No branches or pull requests
2 participants
@Psychlist1972 @AmeNote-Michael