Developer hangs when leaving debug mode

[chrishj]

When I Break out from test mode PL/SQL freezes. This also occurs when waiting at next step.

The version is
PL/SQL Developer
Version 8.0.4.1514
01.61866 - 10 user license
Windows XP Professional 5.1 Build 2600 (Service Pack 3)

Physical memory : 2,097,152 kB (2,023,420 available)
Paging file : 4,194,304 kB (3,399,912 available)
Virtual memory : 2,097,024 kB (1,901,752 available)

Parameters
C:\Program Files\PLSQL Developer\plsqldev.exe

Preferences
Session mode: Multi
OCI Library:
Use OCI7: False

Preference Files
C:\Program Files\PLSQL Developer\Preferences\Default\Default.ini
C:\Program Files\PLSQL Developer\Preferences\Chrishj\default.ini

Plug-Ins

Aliases
ebprd
PEEB
PROD
VPREB

Homes
DevSuiteHome1 (C:\OracleTools\DevSuite)

DLLs
C:\OracleTools\DevSuite\bin\oci.dll

TNS File
C:\OracleTools\DevSuite\Network\Admin\tnsnames.ora

Using
Home: DevSuiteHome1
DLL: C:\OracleTools\DevSuite\bin\oci.dll
OCI: Version 10.1
Oracle Database 10g Enterprise Edition Release 10.2.0.4.0

Character Sets
Character size: 3 byte(s)
CharSetID: 871
NCharSetID: 2000
Unicode Support: True
NLS_LANG: AMERICAN_AMERICA.WE8MSWIN1252
NLS_NCHAR_CHARACTERSET: AL16UTF16
NLS_CHARACTERSET: UTF8

 

[Marco Kalter]

Does this happen for any program unit that you debug? If so, can you let me know the exact steps to reproduce this?

 

[Claus Pedersen]

My guess is that the problem is, some part of the program after the point where the code is break'ed is locking, for instance if the program tries to lock a row that is already locked by another user/program or takes a considerable time to execute. The debugger has the error that is continues to the end of the code, even if a break command is issued. For instance like in the following code:

BEGIN
  do_something;      -- first line
  do_something_else; -- second line, this line locks
END;

Even if a break command is issued at the first line, the program will continue its execution to the second line that eventually will cause the program to lock. Please refer to the last part of the post V8 bug: breaking a debug on 11g database behaves like step out . Could this relate to your problem as well?