Toad World® Forums

Toad 10 hangs after query cancelled

I’ve replicated this issue on both 10.0.0.41 and 10.6.1.

We’ve got a table in a 10.2.0.4 database (connected to via a 10.2.0.2 client) with 3 XMLType columns.

If I do a query on the table but cancel before the results come back, when I do something else in Toad (such as rerun the same or a different query), Toad freezes.

Task manager shows 0% CPU being used.

Is there any chance this could be fixed, please? It’s highly, highly irritating, when I have to reload toad and recover all my editor windows because I forgot about the bug and hit cancel…

Have now upgraded my client to 10.2.0.4, but still Toad (v10.0.0.4 and v10.6.1) hangs.

I can easily recreate this by doing (in the editor):

select * from <my_table_with_xmltype_cols>; (click “execute at snippet at cursor” button)

cancel query

select * from dual; (click “execute at snippet at cursor” button)

The button depresses, but does not release and Toad becomes unresponsive.

*{:frowning:

Attached support bundle stuff (removed some identifying details though)
Toad.ini (45.6 KB)

Attached support bundle stuff (removed some identifying details though)
toad_support_stuff.txt (19.8 KB)

If you run the same query using F5 and try to cancel from there, does Toad hang
there too?

What does the session look like from the Session Browser, any locks or waits?

If I hit F5 and then cancel, I can no longer type anything in the editor window, even though I can open new tabs (can’t type in them, either!). Pressing the stop “hand” button causes Toad to hang.

As for what appears in the session browser - however I executed the query, the session is inactive, with “SQL*Net message from client” as the wait.

ETA: Toad also hangs if I open the table up in describe and then cancel the fetch when I’ve clicked on the data tab, so it’s not just the editor.

When I hit End Task to kill Toad, it immediately pops up saying that Toad isn’t responding, so I’m definitely not imagining the hanging! *{:wink:

Message was edited by: Boneist

I get quite a few hangs in toad when trying to cancel scripts or queries. Almost
not a day goes by when I don’t have to go to the Task Manager and Kill Toad.
I’ve come to accept this because I don’t really have the time to work
the issue. Sometimes I don’t even think that it’s TOAD’s fault.
It’s like Toad submits the cancel to the OCI and then it has to wait.

It’s VERY frustrating! I want to be able to tell toad to do whatever it
takes to return control to me. I don’t care if it leaves sessions open or if
California slides into the ocean I just want control of my window back!
I’m sure there are all kinds of tricky issues in accomplishing this. I wish
you could split toad into separately running jobs like Chrome does with tabs, so
that when you have to Kill, you can just Kill the part that is hung up. At least
Toad saves your work and lets you recover somewhat.

Don’t get me wrong, I love Toad but I have a very short fuse when it comes
to things freezing up especially when the pressure is on me to resolve some
production issue.

Regards,
Mike

On Mon, Apr 11, 2011 at 9:22 AM, Boneist wrote:

Message from: Boneist

If I hit F5 and then cancel, I can no longer type anything in the editor
window, even though I can open new tabs (can’t type in them, either!).
Pressing the stop “hand” button causes Toad to hang.

As for what appears in the session browser - however I executed the query,
the session is inactive, with "SQL*Net message from client" as the wait.

_______________________________________

Historical Messages

Author: Boneist
Date: Mon Apr 11 09:22:46 PDT 2011
If I hit F5 and then cancel, I can no longer type anything in the editor
window, even though I can open new tabs (can’t type in them, either!).
Pressing the stop “hand” button causes Toad to hang.

As for what appears in the session browser - however I executed the query,
the session is inactive, with "SQL*Net message from client" as the wait.
__

Author: Jeff Smith
Date: Mon Apr 11 08:42:05 PDT 2011

If you run the same query using F5 and try to cancel from there, does Toad
hang there too? What does the session look like from the Session Browser,
any locks or waits?

__

Author: Boneist
Date: Mon Apr 11 06:28:45 PDT 2011

Attached support bundle stuff (removed some identifying details though)

__

Author: Boneist
Date: Mon Apr 11 05:23:47 PDT 2011

Have now upgraded my client to 10.2.0.4, but still Toad (v10.0.0.4 and
v10.6.1) hangs.

I can easily recreate this by doing (in the editor):

select * from ; (click "execute at snippet at
cursor" button)

cancel query

select * from dual; (click "execute at snippet at cursor" button)

The button depresses, but does not release and Toad becomes unresponsive.

*{:-(

__

Author: Boneist
Date: Wed Apr 06 09:16:34 PDT 2011
I've replicated this issue on both 10.0.0.41 and 10.6.1.

We've got a table in a 10.2.0.4 database (connected to via a 10.2.0.2
client) with 3 XMLType columns.

If I do a query on the table but cancel before the results come back, when I
do something else in Toad (such as rerun the same or a different query),
Toad freezes.

Task manager shows 0% CPU being used.

Is there any chance this could be fixed, please? It's highly, highly
irritating, when I have to reload toad and recover all my editor windows
because I forgot about the bug and hit cancel...
__
_______________________________________

Evening Michael,

I get quite a few hangs in toad when trying to cancel scripts or
queries.

I run Toad daily as well, sometimes it stays running for a week or more

  • depending on whether I get to leave long running jobs overnight and
    don;t have to switch my PC off to save Power - I work at the Environment
    Agency after all!

I never have Toad hang when I cancel a query. I’m surprised that you do.

I’m running 10.5 at the moment, and I have it configured with auto
commit off, and run everything possible in a separate thread (which is
exactly what Chrome does - one tab one thread - indeed, Firefox 4 does
this too).

Do you have the various options set to allow Toad to execute queries in
separate threads?

Just a thought.


Cheers,
Norm. [TeamT]

Hi Norm,.
If you are talking about the “Apply commit/rollback to all tabs(threaded
queries)” check box, then No, I did not have that selected.
If you are talking about “Execute queries in threads” check box, then No, I also
did not have that selected.

(which is weird because I could swear I checked/selected these)

Anyway, I’ve checked them now and hopefully that will help.

As for Chrome vs Firefox, Chrome starts a new “task” for each browser tab.
Firefox may create separate threads, but it does not start a new “task”. So with
Chrome, you can use the Task Manager" to Kill a specific Task and leave the
others running.

Try it on Chrome and then view the tab you killed. It’s really quite funny.

Thanks for your help Norm,.
Regards,
Mike

On Mon, Apr 11, 2011 at 11:57 AM, Norman Dunbar wrote:

Evening Michael,

I get quite a few hangs in toad when trying to cancel scripts or
queries.

I run Toad daily as well, sometimes it stays running for a week or more
- depending on whether I get to leave long running jobs overnight and
don;t have to switch my PC off to save Power - I work at the Environment
Agency after all!

I never have Toad hang when I cancel a query. I'm surprised that you do.

I’m running 10.5 at the moment, and I have it configured with auto
commit off, and run everything possible in a separate thread (which is
exactly what Chrome does - one tab one thread - indeed, Firefox 4 does
this too).

Do you have the various options set to allow Toad to execute queries in
separate threads?

Just a thought.


Cheers,
Norm. [TeamT]

And by "Task’ I mean ‘Process’.
regards,
Mike

On Mon, Apr 11, 2011 at 12:24 PM, Michael Moore
wrote:

Hi Norm,.
If you are talking about the “Apply commit/rollback to all tabs(threaded
queries)” check box, then No, I did not have that selected.
If you are talking about “Execute queries in threads” check box, then No, I
also did not have that selected.

(which is weird because I could swear I checked/selected these)

Anyway, I've checked them now and hopefully that will help.

As for Chrome vs Firefox, Chrome starts a new "task" for each browser tab.
Firefox may create separate threads, but it does not start a new "task". So
with Chrome, you can use the Task Manager" to Kill a specific Task and leave
the others running.

Try it on Chrome and then view the tab you killed. It's really quite
funny.

Thanks for your help Norm,.
Regards,
Mike

On Mon, Apr 11, 2011 at 11:57 AM, Norman Dunbar
wrote:

Evening Michael,

I get quite a few hangs in toad when trying to cancel scripts or
queries.

I run Toad daily as well, sometimes it stays running for a week or more
- depending on whether I get to leave long running jobs overnight and
don;t have to switch my PC off to save Power - I work at the Environment

    Agency after all!

    I never have Toad hang when I cancel a query. I'm surprised that you
    do.

    I'm running 10.5 at the moment, and I have it configured with auto
    commit off, and run everything possible in a separate thread (which is
    exactly what Chrome does - one tab one thread - indeed, Firefox 4 does
    this too).

    Do you have the various options set to allow Toad to execute queries in
    separate threads?

    Just a thought.


Cheers,
Norm. [TeamT]

Hi Mike,

On 11/04/11 20:26, Michael Moore wrote:

And by "Task’ I mean ‘Process’.
regards,
Mike
Sigh! So did I! When I said “thread”. One day, I’ll get something
technical right!

Sorry about the inability to type what I was thinking. :frowning:

And I don’t have my "apply commit/rollback to separate threads checked,
just the other one. I like to retain command of what gets committed -
hence I always turn auto commit off.


Cheers,
Norm. [TeamT]

I can reproduce this, but I’m having a tough time figuring it out. It
really looks like the OCI is getting stuck….

I get quite a few hangs in toad when trying to cancel scripts or queries. Almost
not a day goes by when I don’t have to go to the Task Manager and Kill Toad.

I used to have the same thing happen, but switching to the run queries in threads option helped enormously! Now I don’t have a problem, except when I forget and cancel a query on a table with XMLTYPE columns! (Usually when I’ve forgotten to add a where clause before running the query!)

I’m seeing the same behavior in version 10.6. Cancelling any long running query or script is causing Toad to hang. I had to cancel the Toad process three times in one day. Toad 9.7 did not have this problem, so I am using it instead.

This looks to be fixed in v11 \o/

Awesome work, John!

I’m not sure that I can take credit for it, but I’m glad it’s
working!