Kevin Seymour
Member²
I have found that the following combination of actions will cause PL/SQL Developer to hang indefinitely:
1) Run some PL/SQL in a test window that makes a change (commit/ rollback buttons will enable)
2) Step through some PL/SQL in that same window without committing or rolling back
3) While the debugger is paused waiting for you to step click rollback
The program now hangs and must be killed via task manager. I think while debugging the commit and rollback buttons should be disabled again.
1) Run some PL/SQL in a test window that makes a change (commit/ rollback buttons will enable)
2) Step through some PL/SQL in that same window without committing or rolling back
3) While the debugger is paused waiting for you to step click rollback
The program now hangs and must be killed via task manager. I think while debugging the commit and rollback buttons should be disabled again.
