FloDee has been flagged by Defender as malware.

It's a memory leak. It has been there forever but getting FloDee to function correctly was more important than a icon sized memory leak on a product not even ready for release. And since it forced me to find the leak, it winds up being a call to add an object to a flowlayoutpanel (pic attached). That's a winform call.

===========================================================================

===========================================================================

Also, that leak has been there from the start. How come it never raised any flags till I called it beta? None the less, it will have to contact MS over it to get it cleared up. I have no control over those API calls. They are winform calls and shouldn't be stealing memory. I'm passing the correct data or else the icons wouldn't show up at all.  Defender lists it as a user32/persistent violation. But that's not what people see. All they see is MALWARE!!  So I am kinda pissed. Defender has not saved the world from an icon sized memory leak (yep it's a bitmap the size of an icon), but they have scared anybody who has downloaded. And why now?.. when that bit of code has been there since last year?

Guess I will set the project to draft till I get it squared away. I don't write malware and FloDee has none.  It is a bug, being reported by Microsoft as malware.  So I will will be contacting MS with a video showing their task manager report a memory leak on FloDee ONLY when those 2 calls are made. And it's either of them. If I remove only one, it still leaks. Only upon commenting out both lines will the leak go away.  Will post a video of it.