Oracle Database Discussions

I'm not sure posting here is the right place, since it happens using SQL Developer, but nobody can help there...

While debugging a stored procedure, network use on the database goes waaaaay up to taking up more than 3/4 of the resources. Analyzing the wait events of the debugging session, almost all the time waited is for "TCP Socket (KGAS)".
After running the procedure for about a minute, the session hangs in one of the "TCP Socket (KGAS)" events, counting eternally the "Seconds in wait", not advancing anymore. If during this minute I hit a breakpoint and debug step by step, the minute-to-hang gets paused also. So after about a minute of summed running time, the session hangs.
SQL Dev isn't aware of this hung session, and appears to continue running the procedure (only that it's not advancing). The only thing I can do is kill the session on the database OS (killing through the database won't free the acquired locks and stuff). This wakes up SQL Dev instantly (saying the session has been killed), so I can start another debug run.
And so on...
Debugging big slow procedures is really no fun like this. I constantly have to monitor the wait events and if there's a "TCP Socket (KGAS)" that takes more than 5 seconds, I know the session is lost in socketland.

Does anyone know something about the "TCP Socket (KGAS)" wait event? Did anyone notice the same behaviour? Does anyone has a suggestion for more solid debugging? Anything?

Hoping for some kind of magical solution proposed by some kind of Oracle/networking guru,
K.