UPDATE: We resolved this by doing away with the third party image object and began using PowerBuilder's web object.. Thank you all.
Hello PB Community!
Since migrating from PB2017 to PB2021 we've begun experiencing what seems to be an issue with memory with our executables (which are 64 bit BTW). We have a 3rd party image display system sitting on an OLE object that, after time, the PowerBuilder buttons and fonts become larger, and bold, and the images start to not come up, or some do and some don't. So, I started monitoring the memory (what little I know about it is about ready to be evident) in the Resource Monitor. What I see happening is when we open the the window the thread count increases by 6 or 7, and when we close said window (with objects being destroyed and garbage collection, etc.), the thread count only diminishes by 3.
Once that thread count reaches between 200 & 250 (rough numbers, it varies I'm sure because other things are happening on the system) we start experiencing the odd behavior and the only way to remedy it is to completely shut down and restart the application.
I've gone back to our PB 2017 built application and monitored the same activities and the thread count behavior is what you would expect it to be. Increases by 3, then decreases by 3 when we close the application. I have yet to be able to get the thread count over 15. No code changes were made prior to the migration, so the code base is identical.
Any thoughts, suggestions, offers of tequila would be appreciated! Truly.
Happy Monday!
MJ
MJ