I discovered that in CTD63 SP1 and CTD61 SP2 popup menus do not release user objects:
after several openings of the popup menus the program crashes (reaches user object limit of 9999 items).
SalReportPrint function in CTD63 sp1 Windows 10 also does NOT release user objects;
Instead CTD63 SP1 WORKS fine under WIN7, WIN8, WIN2012 O.S.
In CTD61 sp1 works correctly at anytime in any O.S. condition
Is it possible to close user objects?
Any idea to solve the problem?
Attached a test program.
- Founder/Site Admin
- Posts: 3384
- Joined: 24 Feb 2017, 09:12
- Location: Gouda, The Netherlands
https://wiki.tdcommunity.net/index.php/S ... ry_process
I tested your sample on the latest TD 6.3.9 version and no leaks are present.
I recall that some earlier TD versions had this and is resolved.
To my knowledge you are unable to fix it yourself as the handles are created and maintained within the TD runtime and are not accessible from outside.
(though you might get a list of opened handles using WinAPI and make a manager which detects new handles and when you know which one to release you can do it from code.
But I think this is a fairly unreliable task)
I'm afraid the best option is to upgrade to the latest TD version.
Who is online
Users browsing this forum: [Ccbot] and 5 guests