Hi, Thank you for the answer. Unfortunately reduzid test case is hard to create. Likely is MS Windows especific bug (iupwinBaseMsgProc), but I think the cause is the same: IupiupObjectCheck dereference a freed pointer.
Best regards, Ranier ________________________________________ De: [email protected] <[email protected]> Enviado: segunda-feira, 2 de outubro de 2017 11:51 Para: [email protected] Assunto: [Iup-users] Memory problems from Dr.Memory Hello Ranier, In previous messages you have pointed to some memory problems. https://sourceforge.net/p/iup/mailman/message/36053676/ https://sourceforge.net/p/iup/mailman/message/36053696/ Let's take the discussion off the localization thread and discuss them in a separate thread. That's hard to say what could be a problem by just looking at the callstack. It would be best if you could boil down the issue to a simple test code that would replicate the errors. Or at least try to describe your test case. Also, I don't use Windows, so I won't probably be able to help if the problem is specific to MS Windows only. Best regards, blueowl ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Iup-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/iup-users ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Iup-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/iup-users
