I run a script in SQL Editor. The script is working or waiting...anyway running.
Now I wanna open the Tools > Session Browser (SB) to see maybe - what is my script there for so long.
The thing is - the script may never end if some locks are involved or the script is not well written.
So as a result not only the SB is not opened but SQLnav hangs...for as long as the script is running.
The workaround is to open a new SQLnav instance, but I suggest to have an option to open the SB in another session.
(Or at least warn the user that the session is busy. Because not always the green line, that indicates that the session is busy, is in my sight)