6.0.2 needs how much memory?

[MarkP]

Hello Marco,

PLSQLDEV 6.0.2 displays a "Thread Creation Error: Not enough storage is available to process this command" message, when I try to view a package body, and Windows Task Manager presently reports Mem Usage of 256588K for plsqldev.exe, much more than I recall version 5 needing.

While I've been typing this, the Mem Usage figure has crept up to 256612K.

Could the program be leaking? If such a high memory usage is unusual, then please tell me what I can do to help the team find the cause.

256928K ... I think I'd better close it.

Kind Regards, Mark.

 

[Marco Kalter]

My PL/SQL Developer instance takes up 34MB, so 256MB would be unusual. Is this reproducable when you restart PL/SQL Developer? If so, can you send me the package body that causes this problem?

 

[MarkP]

Thank you, Marco, but it wasn't a problem with any particular package body, it happened whenever I selected View from the object browser.

I'm sorry, but I cannot reproduce the behaviour on demand. As soon as it recurs, I shall send you the source of the object concerned.

I presently suspect that the leak (if that it is) might be caused by a SELECT that returns collection and CLOB columns. That causes its SQL Window to lock (I have to kill PLSQLDEV when it happens), whenever it's rerun after a connection failure and Log On. This behaviour is reproduced easily:

(1) Run SELECT that returns collection and CLOB columns (records per page automatically determined);

(2) Break network connection -- using Hibernate, as if you were going home, for example ;

(3) Reconnect network and log-on to PLSQLDEV;

(4) Repeat (1) ... and wait.

I hope that your team enjoy that, since I'm off on holiday now.

Kind Regards, Mark.