Over the last 6 months i’m in contact with the TOAD Support, because of massive memory problems by using TOAD 12.8. on a VM with Windows XP. I know XP is old, but our complete ORACLE development platform is still installed on XP and i still need to use TOAD on that platform.
Now i have installed 12.9 beta (2 days ago) and i until now i have no memory problems, good news. But i still have the same problems as in Version 12.8 with error Messages like that:
I have already sent that to TOAD Support but they said, i should post the Errors in that beta Forum.
i’m sorry, but i’m new in this Forum and i have created the Support bündle txt file, but i don’t know how to upload it here. Can you give a hint, please?
i'm sorry, but i'm new in this Forum and i have created the Support bündle txt file, but i don't know how to upload it here. Can you give a hint, please?
Regarding the screen captures: i made These captures directly from the Screen and paste it into the web site here. That doesn’t work? - So, do i always have to save the Screen shot locally as a file and then upload the file? - Or does it work, if i reply by email including the Screen shots? Support_bundle_12_9_20160413.txt (99.5 KB)
One thing that jumps out is that your Toad has been running for 29 hours. On older Operating systems, you should really not leave apps running full time like that. Even a small memory leak is magnified when it never has a chance to clean up..
Does that mean, it should be a better practise to shut down TOAD every evening? - Or is it necessary to shut down the VM every evening to run TOAD correctly?
One thing that jumps out is that your Toad has been running for 29 hours. On older Operating systems, you should really not leave apps running full time like that. Even a small memory leak is magnified when it never has a chance to clean up…
Best practice for Toad (and any Windows 32 bit app) is to shut it down at least once a day. These desktop apps are simply not designed to be running 24/7. WinXP also had issues cleaning up after itself so even in a VM, you should restart it periodically as well. If you google for Windows XP memory leak, there are a lot of hits. Remember you're talking about a 15 year old operating system so the old tech support saying "did you restart your computer?" still applies to your situation.
Does that mean, it should be a better practise to shut down TOAD every evening? - Or is it necessary to shut down the VM every evening to run TOAD correctly?
From my point of view, until TOAD Version e.g. 11.6 i never have such problems with memory or Error messages. And i always use the same windows version. So, i will follow you with shutting everything down as often as i can. But TOAD still supports XP and i can not really understand why version 11.6 runs much better than 12.8 / 12.9.
Best practice for Toad (and any Windows 32 bit app) is to shut it down at least once a day. These desktop apps are simply not designed to be running 24/7. WinXP also had issues cleaning up after itself so even in a VM, you should restart it periodically as well. If you google for Windows XP memory leak, there are a lot of hits. Remember you’re talking about a 15 year old operating system so the old tech support saying “did you restart your computer?” still applies to your situation.
The key editor component was replaced a few versions ago and there was a memory leak introduced in v12.8. We're still working on a complete fix for it but the longer Toad stays open, the more likely the leak is to manifest itself and it will manifest itself faster on an older operating system. One other thought is that since Microsoft no longer supports XP, you should really consider upgrading at least to Windows 7. We still support it because we have quite a number of users still using it and we don't want to throw you under the bus but Microsoft already has.
Reply by Michael.Roeder
Ok, understand, thank you.
From my point of view, until TOAD Version e.g. 11.6 i never have such problems with memory or Error messages. And i always use the same windows version. So, i will follow you with shutting everything down as often as i can. But TOAD still supports XP and i can not really understand why version 11.6 runs much better than 12.8 / 12.9.
Yes, you’re right about XP and upgrade to WIN 7. Of course this is our problem that we’re “a little” late upgrading our complete oracle development paltform to an newer release.
But as is said before, i know about that problem, but i haven’t problems with TOAD until version 11.6 or so and in gerneral newer version shouldn’t have more problems as older versions.
The key editor component was replaced a few versions ago and there was a memory leak introduced in v12.8. We’re still working on a complete fix for it but the longer Toad stays open, the more likely the leak is to manifest itself and it will manifest itself faster on an older operating system. One other thought is that since Microsoft no longer supports XP, you should really consider upgrading at least to Windows 7. We still support it because we have quite a number of users still using it and we don’t want to throw you under the bus but Microsoft already has.
Agreed. We didn't find out about the memory leak in 12.8 until well into the start of the 12.9 development cycle and when 12.9 is released in June, we will have the issue fully resolved. Unfortunately, the only workaround for 12.8 is to restart Toad periodically.
Reply by Michael.Roeder
Yes, you're right about XP and upgrade to WIN 7. Of course this is our problem that we're "a little" late upgrading our complete oracle development paltform to an newer release.
But as is said before, i know about that problem, but i haven't problems with TOAD until version 11.6 or so and in gerneral newer version shouldn't have more problems as older versions.
Agreed. We didn’t find out about the memory leak in 12.8 until well into the start of the 12.9 development cycle and when 12.9 is released in June, we will have the issue fully resolved. Unfortunately, the only workaround for 12.8 is to restart Toad periodically.
What Greg said. 12.8 introduced a memory leak that was not present in 12.7 or earlier. It is pretty severe and a few hours of running Toad could wreak havoc. 12.9 beta should have it nailed so if you are able to use it please do so and let us know what comes of it.