I see that you are using a 64 bit Oracle19 client. We have one more problem report like this for this exact client configuration. Even though we have not been able to reproduce this issue, the customer was able to resolve this by using the 32 bit version of PL/SQL Developer and a 32 bit Oracle Client.

As a test, can you download the 32 bit version of PL/SQL Developer and check if this resolved the issue for you too?

I have the exact same behavior when using 32-bit versions of the same software.

Marco, any other suggestions? It's pretty impossible to not break queries.

At the moment I can only suggest that you try a previous Oracle Client version. Can you try this with an Oracle12 Client?

It works correctly with the 12c client.

Okay. We'll continue to investigate.

Hey.
99% of times I try to break execution it is not working since we installed version 14.02.1969. Maybe something changed recently? Before it was +/- fine.

EDIT: Ok, 99% of times is a little bit too harsh, but the bottom line is - lately something has changed to worse with this. Idk, looked through latest update changelog, couldn't find anything related.

The break function has not changed recently.

If/when break does not work for me and I don't want to wait, I open another PL/SQL Developer. Then I use the sessions tool to kill the session.

Got another complaint from a co-worker that the cancel SQL is no working anymore.
We're using version 14.0.3.1981.
Killing sessions is not an option because there are databases where I don't have ALTER SYSTEM priviliges.
We can try closing the SQL window and PLSQL developer offers a button "Terminate". But when I press that, plsqldev becomes not responding and the only option is to kill it.