Hi Holger, Is there an open pull request on the OpenEXR github with this patch? Seems like a good place to raise awareness.
* Nick From: Schoenberger<mailto:x...@digidragon.de> Sent: Tuesday, February 28, 2017 1:58 AM To: openexr-devel@nongnu.org<mailto:openexr-devel@nongnu.org> Subject: Re: [Openexr-devel] Windows Dr.Memory and OpenEXR Hi Oh, yes. I updated the zip file with the ImfAttribute files. Holger Schönberger technical director The day has 24 hours, if that does not suffice, I will take the night From: Gonzalo Garramuño [mailto:ggarr...@gmail.com] Sent: Monday, February 27, 2017 9:53 PM To: Schoenberger Cc: openexr-devel@nongnu.org Subject: Re: [Openexr-devel] Windows Dr.Memory and OpenEXR El 27/02/2017 a las 08:54, Schoenberger escribió: Note: I have tested 2.0.0 with Visual Leak Detector. I did not got a crash, but you will encounter a memory leak once your app does not crash any more. It is a known tiny memory leak in OpenExr. But it is allocated once for the whole lib and does not increase. I have found a fix in an old post of this list. I do not know why it was not added, so I did not ask to add it as well. Anyway, if you want to have a fix, please check this zip: www.BinaryAlchemy.de/download/openexr-2.2.0_source_change.zip<http://www.BinaryAlchemy.de/download/openexr-2.2.0_source_change.zip> Thank you for the heads up and the source changes. However I found that the static Attribute::clearAttributeRegistration() was missing. Maybe you need to add another file to the source change. -- Gonzalo Garramuño
_______________________________________________ Openexr-devel mailing list Openexr-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/openexr-devel
