Hi,
Just curious… when running a long query, the app becomes unresponsive after a while - so you’re unable to Cancel it, as the window becomes frozen and Windows ask you either to wait or close it.
I know you can enable the “Execute queries in threads”, but why the system is working and able to cancel for some time until not anymore? Any way to increase how long it’s “alive”?
Regards,
When we run a long non threaded query, we send a command to Oracle and wait for a response.
If the wait is too long, then yeah the app can appear frozen. Toad doesn't control that, windows does. I just googled how long it takes and if you can adjust that. I found this but did not test it.
Short answer (untested): Add/Edit HungAppTimeout to HKEY_CURRENT_USER\Control Panel\Desktop . Value is in milliseconds (I think default is 5000). Restart.
Note: This value also controls how long windows will wait on an app when shutting down.
OMG, this is a game changer (it works!!). I searched for more info about applying it to specific app(s) only but I just found this - not sure if worth to try:
Disable Window Ghosting (For Developers): If you are the developer of the app, you can call the Windows API function DisableProcessWindowsGhosting() within your code. This prevents the OS from ever marking your app's window as "Not Responding".
Regards,
I am (one of) the developers, but I don't think I want to disable that completely for Toad. Good to know though.
Sure, I know 
I just copied IA’s reply about this. I’m not sure if there’s any good of allowing the app to “freeze”, specially in this specific one (a common use case is having long queries running - making the app not accesible until it finishes doesn’t seem right either).
Maybe you could give it a try in one of the betas and see how it goes.
Best,
It's kind of a balancing act. We know there are some things in Toad that we have to sometimes have to wait on, but other times there are things that are legitimately taking longer than they should. I don't want to disrupt the way windows normally handles that situation unless I need to. In your initial situation - cancelling a query - does waiting help, or is Toad truly stuck? I have heard cases of Toad getting stuck while trying to cancel for some users, but haven't been able to reproduce or fix it.
Also - I have found one good use of that "not responding" dialog, which I documented in this post.
No, for me when I launch a long query, TOAD becomes unresponsive after a few seconds (well, not anymore it seems after the registry change). I’m unable to do anything or recover it, so it becomes unusable until the query ends or I kill the session manually.